fz0x1/HPI
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Rename my_configuration to mycfg for brevity

Browse source
This commit is contained in:
Dima Gerasimov 2019-12-19 19:45:25 +00:00 • committed by Dmitrii Gerasimov
parent cd804091c3
commit 066641a4ce
31 changed files with 65 additions and 70 deletions
Download patch file Download diff file Expand all files Collapse all files

10
misc.org
View file

@ -13,23 +13,23 @@ Various thoughts on organizing
- not mypy/pylint friendly at all?
- Second alternative:
symlinks in my_configuration and direct import?
symlinks in mycfg and direct import?
+ mypy/pylint friendly
? keeping a symlink to model.py is not much worse than hardcoding path. so it's ok I guess
* Thoughts on organizing imports
- First way:
import my_configuration.hypexport_model as hypexport
works, but my_configuration is scattered across the repository?
import mycfg.hypexport_model as hypexport
works, but mycfg is scattered across the repository?
Second way:
from . import my_configuration?
from . import mycfg?
doesn't seem to work with subpackages?
right, perhaps symlinking is a good idea after all?...
Third way:
import my_configuration.repos.hypexport.model as hypexport
import mycfg.repos.hypexport.model as hypexport
works, but MYPYPATH doesn't seem to be happy...
ok, --namespace-packages solves it..