naming-conventions

问题 Is that really true that i can use $_ as a dummy variable in foreach loop if there is no need for $value in foreach($array as $key => $value) ? I could not find any useful information that proves this except PHP syntax formatting. There's a special case for foreach loops when the value is not used inside the loop. In this case the dummy variable $_ (underscore) is used: foreach ($GLOBALS['TCA'] as $table => $_) { // Do something with $table } This is done for performance reasons, as it is

问题 Is that really true that i can use $_ as a dummy variable in foreach loop if there is no need for $value in foreach($array as $key => $value) ? I could not find any useful information that proves this except PHP syntax formatting. There's a special case for foreach loops when the value is not used inside the loop. In this case the dummy variable $_ (underscore) is used: foreach ($GLOBALS['TCA'] as $table => $_) { // Do something with $table } This is done for performance reasons, as it is

问题 Is that really true that i can use $_ as a dummy variable in foreach loop if there is no need for $value in foreach($array as $key => $value) ? I could not find any useful information that proves this except PHP syntax formatting. There's a special case for foreach loops when the value is not used inside the loop. In this case the dummy variable $_ (underscore) is used: foreach ($GLOBALS['TCA'] as $table => $_) { // Do something with $table } This is done for performance reasons, as it is

问题 What is the preferred naming convention for Django model classes? 回答1: Django models are just Python classes, so the Python naming conventions detailed in PEP-8 apply. For example: Person Category ZipCode If Django fails to pluralize the class name properly when creating the corresponding table, you can easily override the pluralization by setting a custom verbose_name_plural field in an inner META class. For example: class Story(models.Model): ... class Meta: verbose_name_plural = "stories"

问题 What is the preferred naming convention for Django model classes? 回答1: Django models are just Python classes, so the Python naming conventions detailed in PEP-8 apply. For example: Person Category ZipCode If Django fails to pluralize the class name properly when creating the corresponding table, you can easily override the pluralization by setting a custom verbose_name_plural field in an inner META class. For example: class Story(models.Model): ... class Meta: verbose_name_plural = "stories"

来源： https://stackoverflow.com/questions/42127593/should-python-class-filenames-also-be-camelcased

来源： https://stackoverflow.com/questions/5096025/should-class-specific-constants-still-be-declared-at-module-level

来源： https://stackoverflow.com/questions/63222197/does-python-garbage-collector-behave-any-different-with-a-single-underscore-va

来源： https://stackoverflow.com/questions/63222197/does-python-garbage-collector-behave-any-different-with-a-single-underscore-va

问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 5 years ago . Improve this question I was used to naming my JUnit Integration tests with a *Test.java on the end eg DatabaseConnectionTest.java and placing them in their own integration test directory: eg test/integration/com... On joining a new project I was directed No, all the Tests go