[issue29144] Implicit namespace packages in Python 3.6

2017-07-31 Thread Lumír Balhar
Lumír Balhar added the comment: Thank you for the replies. I created an issue [0] on setuptools GitHub (without reply yet) because I also think that setuptools should install pkg_resources-style __init__.py files. [0] https://github.com/pypa/setuptools/issues/1097 --

[issue29144] Implicit namespace packages in Python 3.6

2017-07-19 Thread Nick Coghlan
Nick Coghlan added the comment: At the Python level, the rules are simple: the first directory on sys.path that contains an __init__.py file is identified as a self-contained package. It is then up to that __init__.py file to emulate namespace package behaviour (by extending __path__) if that'

[issue29144] Implicit namespace packages in Python 3.6

2017-07-19 Thread Brett Cannon
Brett Cannon added the comment: Without looking into what changed, I say Python 3.6 being more strict in what is a namespace package is reasonable and setuptools needs to be better about installing pkg_resources-using __init__.py files. -- ___ Pytho

[issue29144] Implicit namespace packages in Python 3.6

2017-07-19 Thread Lumír Balhar
Lumír Balhar added the comment: Hello. I've tried the build of python-moksha-common on Fedora rawhide [0] and Fedora 25 [1]. Fedora rawhide: Python 2.7.13 and 3.6.1, setuptools 36.2.0 Fedora 25: Python 2.7.13 and 3.5.3, setuptools 25.1.1 Source tarball of moksha.common contains pkg_resources-

[issue29144] Implicit namespace packages in Python 3.6

2017-07-18 Thread Nick Coghlan
Nick Coghlan added the comment: Are you able to confirm the version of setuptools involved is the same in both cases? The reason I ask is that the interaction between pkg_resources-style namespace packages and native ones is known to be temperamental (https://packaging.python.org/guides/packa

[issue29144] Implicit namespace packages in Python 3.6

2017-07-18 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +brett.cannon, eric.snow, ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue29144] Implicit namespace packages in Python 3.6

2017-07-18 Thread Lumír Balhar
Lumír Balhar added the comment: Hello. I've met this issue again in moksha project [0] where namespace package is used. - module moksha.common is installed via RPM to site-packages and there isn't file moksha/__init__.py so the implicit way to create namespace package is used there. - moksha.

[issue29144] Implicit namespace packages in Python 3.6

2017-03-27 Thread Charalampos Stratakis
Charalampos Stratakis added the comment: Bumped upon a similar issue today where a package I was working on couldn't import a module from one of its dependencies (which was not the case in python 3.5). One of the lines that fail is this [0] with: ModuleNotFoundError: No module named 'repoze.wh

[issue29144] Implicit namespace packages in Python 3.6

2017-01-04 Thread Tomas Orsava
Changes by Tomas Orsava : -- nosy: +torsava ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue29144] Implicit namespace packages in Python 3.6

2017-01-03 Thread Eric V. Smith
Changes by Eric V. Smith : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue29144] Implicit namespace packages in Python 3.6

2017-01-03 Thread Lumír Balhar
New submission from Lumír Balhar: Hello. I've found a really strange difference between Python 3.5 and 3.6 related to namespace packages and I cannot find any note in changelogs. I've created a simple bash script which can reproduce my issue using virtual environments: http://pastebin.com/j3f