Change by Sebastian Koslowski :
--
nosy: +skoslowski
___
Python tracker
<https://bugs.python.org/issue40059>
___
___
Python-bugs-list mailing list
Unsubscribe:
Sebastian Koslowski added the comment:
>>> import parent.child
first imports "parent" (successfully) but then fails, because the import code
has no knowledge of were to find ".child". This is because
a) the module "parent" is not marked as a package (
Sebastian Koslowski added the comment:
I ran into this issue on a Win10 German box running the tests for version 3.7.4
Your changes fixes the issue for me.
--
nosy: +skoslowski
versions: +Python 3.7 -Python 3.8
___
Python tracker
<ht
Sebastian Koslowski added the comment:
So, I dug into this here at the PyCon19 sprints and as far as I can see there
is no actual leak.
What you are seeing in your code example is from the state, that is kept
between successive run of your import. All the cases you reported as not
leaking
Change by Sebastian Koslowski :
--
keywords: +patch
pull_requests: +13028
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Sebastian Koslowski added the comment:
I would like to work on this.
--
nosy: +skoslowski
___
Python tracker
<https://bugs.python.org/issue36275>
___
___
Pytho
Sebastian Koslowski added the comment:
I ran into the same problem.
Seems like adding an empty sys.path entry through the _pth file is not
supported at the moment:
https://github.com/python/cpython/blob/53b9e1a1c1d86187ad6fbee492b697ef8be74205/PC/getpathp.c#L589
For now, I have enabled