Move code out of __init__.py
See original GitHub issueSome __init__.py
files contain quite a lot of code. We should move the code to proper files.
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (9 by maintainers)
Top Results From Across the Web
python - Moving code out of __init__.py but ...
I'm working on a Python project where a previous developer placed a large portion of the code in the base __init__.py file. I...
Read more >Understanding Python imports, __init__.py and pythonpath
When do we need __init__.py? First, let's try importing the utils directory within example3_outer.py (after commenting out all the existing code):
Read more >What is __init__.py? and what should I put in it?
The most minimal thing to do is to leave the __init__.py file totally empty. Moving slightly away from this, while still keeping things ......
Read more >How to create a Python Package with __init__.py
First, lets move our scripts into a new subfolder and call it: string_func . Then create an empty file in that folder called...
Read more >What's your opinion on what to include in __init__.py ? : r/Python
It also decouples your public API from your code. You may want to change ... Is the version being in init.py useful outside...
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 FreeTop 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
Top GitHub Comments
Just about the
__init__.py
files, for example, this one here.@pranavdurai10 Sure. Thanks for taking this over 👍