Postpone importing packaging in `env.py`
See original GitHub issueTo simplify bootstrapping we should only import packaging
inside the functions where it’s used. This would eliminate two dependencies, packaging and pyparsing, which are currently required to bootstrap build.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How to avoid circular imports in Python? - Stack Overflow
In some cases, just importing a module with a circular import dependency can result in errors even if you're not referencing anything from...
Read more >Error when importing TensorFlow | Apple Developer Forums
When I try to import tensorflow: import tensorflow. I get the following error: RuntimeError: module compiled against API version 0xe but this version...
Read more >sloria/environs: simplified environment variable parsing - GitHub
environs is a Python library for parsing environment variables. It allows you to store configuration separate from your code, as per The Twelve-Factor...
Read more >How to Manage Python Dependencies with Virtual ...
In this case, Pipenv will automatically import the contents of the requirements file and create a Pipfile. To ensure all the packages have...
Read more >How to Fix : “ImportError: Cannot import name X” in Python?
You can solve the “ImportError: Cannot import name X” Error by resolving the circular dependencies. You can do that either by eliminating ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thank you! I just merged it 😊
Hello @layday @FFY00 👋🏻 . Just tried to address this issue using PR: #395. Please take a look.