René's URL Explorer Experiment

Title: Extract all "import gc" to module level by EliahKagan · Pull Request #1765 · gitpython-developers/GitPython · GitHub

Open Graph Title: Extract all "import gc" to module level by EliahKagan · Pull Request #1765 · gitpython-developers/GitPython

X Title: Extract all "import gc" to module level by EliahKagan · Pull Request #1765 · gitpython-developers/GitPython

Description: The gc module was already imported at module scope in git/repo/base.py. Although it was moved recently, it is not a new addition. It has been present for about seven years, since f1a82e4 (#555). Importing the top-level git module or any submodule of it runs that import statement: >>> import sys >>> "gc" in sys.modules False >>> import git >>> "gc" in sys.modules True Because the gc module is already imported, reimporting it is fast. Imports that there is no specific reason to do locally should be at module scope. Having them local decreased readability, in part because of how black inserts a black line between them and gc.collect() calls they are imported to allow. An alternative to this change would be to remove the preexisting top-level import gc (there is also another one in the test suite) and replace it with a local import as well. I am unsure if that would affect performance and, if so, whether the effect would be good or bad, since the small delay of the import might potentially be less desirable to an application if it occurs while the work of the application is already in progress. If a gc.collect() call runs as a consequence of a finally block or __del__ method being called during interpreter shutdown, then in (very) rare cases the variable may have been set to None. But this does not appear to have been the intent behind making the imports local. More importantly, a local import should not be expected to succeed, or the imported module usable, in such a situation. Conceptually unrelated to this, it looks like the newly released version of black fails to install on Cygwin in the test-cygwin.yml workflow. I expect failures from that workflow for this reason. Although unrelated, there is of course no rush on this PR, and if that does happen, it would prevent any Cygwin tests from running until a fix or workaround is applied. If that is fixed first, this PR could be rebased. If this problem doesn't happen, then it is resolved or somehow specific to the setup in my fork and on my local machine, in which case probably nothing has to be done about it.

Open Graph Description: The gc module was already imported at module scope in git/repo/base.py. Although it was moved recently, it is not a new addition. It has been present for about seven years, since f1a82e4 (#555). Im...

X Description: The gc module was already imported at module scope in git/repo/base.py. Although it was moved recently, it is not a new addition. It has been present for about seven years, since f1a82e4 (#555). Im...

Opengraph URL: https://github.com/gitpython-developers/GitPython/pull/1765

X: @github

direct link

Domain: github.com

Links:

Viewport: width=device-width