Thanks so much. This is very helpful! But what if we r still developing the codes? I mean the package is not complete, and thus we don't want to install it into the library. What should we do in such a case if we are using the Spider or VSCode? I know PyCharm has the functionality to define where is the root of project file.
thanks so much for ur valuable reply. while do we need to `pip install -e ` multiple times as we constantly develop the codes? Or it's just one-time installation but works as the coding progresses? Besides, as i'm using customed env in miniconda, can we keep it clean after installing my own package? And when debugging the codes, we'll use the codes in the lib directory or still the raw codes in the folder? sorry to bother u with so many questions. really appreciate ur patience
Typically you don't run your script from root... but from somewhere you might have your data to work on so that doesn't work. The other method of python -m .... is also a headache to write. Installing package... just doing the monkey-work over and over. I'm really disappointed with python. This is just terrible.
![[ERROR FIXED] “Attempted relative import in non-package” even with __init__.py](http://i.ytimg.com/vi/pm1IK0fBuhw/mqdefault.jpg)
![[ERROR FIXED] “Attempted relative import in non-package” even with __init__.py](/img/tr.png)
Thank you so much, that saved my working day!
Thanks so much. This is very helpful! But what if we r still developing the codes? I mean the package is not complete, and thus we don't want to install it into the library. What should we do in such a case if we are using the Spider or VSCode? I know PyCharm has the functionality to define where is the root of project file.
You can install the package in an editable mode.
```
pip install -e
```
This means you can keep coding new things into the package.
thanks so much for ur valuable reply. while do we need to `pip install -e ` multiple times as we constantly develop the codes? Or it's just one-time installation but works as the coding progresses? Besides, as i'm using customed env in miniconda, can we keep it clean after installing my own package? And when debugging the codes, we'll use the codes in the lib directory or still the raw codes in the folder? sorry to bother u with so many questions. really appreciate ur patience
@@jimmy_bytheway_1112 No you don't have to it works even when you create new folders!
import sys
sys.path.append("..")
try: from ..user.apps.Calculator import *
except: from ..user.apps.Calculator import *
calc.main()
Doesn't work. Why?
what's the error?
@@chinamatt ImportError: attempted relative import with no known parent package
Very helpful!
Happy to hear it!
try except thing is unique, I have never seen anybody else using this
Typically you don't run your script from root... but from somewhere you might have your data to work on so that doesn't work.
The other method of python -m .... is also a headache to write.
Installing package... just doing the monkey-work over and over.
I'm really disappointed with python. This is just terrible.
u saved my life hehehe tsk