ADataGman added the comment:
Terry, thank you for the detailed list of alternatives on how to approach
this, that's helpful in how to tackle this issue in my current development.
Nick, for the relative imports of relative imports I think the error
message is fine. It makes sense. It doesn't ne
Terry J. Reedy added the comment:
AData> You log and output show that you problem is as described: package
'sound' is in directory "C:/" and "C:/" is not is sys.path. Possible remedies:
1. Add "C:/" to sys.path at the top of each module that imports sound. This is
a nuisance.
2. Move the so
Nick Coghlan added the comment:
As discussed in
http://python-notes.curiousefficiency.org/en/latest/python_concepts/import_traps.html#executing-the-main-module-twice
and https://www.python.org/dev/peps/pep-0395/#why-are-my-imports-broken the
cryptic error message here is due to the relative
ADataGman added the comment:
Here's the full error log I receive when using the code I submitted with
both ..effects and sound.effects. It also includes a print out of the sys
path as run from vocoder.
I tried running this in 3.7.2 and still get the same errors. It seems like
it's already on t
Terry J. Reedy added the comment:
When reporting problems, copy and paste into the report the complete exception
traceback and error message. For import problems, also copy and paste
sys.path. If you disagree that this should be closed, please do so.
--
___
Terry J. Reedy added the comment:
3.6 only gets security patches.
I cannot comment on relative imports as I never use them, but the absolute
imports should work and do for me. I just added to idlelib.idle_test a file
a.py containing 'from idlelib.idle_test import htest' and it works find.
New submission from ADataGman :
Attempting to follow
https://docs.python.org/3.6/tutorial/modules.html#intra-package-references I
was unable to recreate the intra-package reference as described.
"For example, if the module sound.filters.vocoder needs to use the echo module
in the sound.effe
