Repository navigation
Importing backports and moves packages, imports (e.g. test.py) fromuser folders, #268
Description
Activity
- added a commit that references this issue
on Mar 20, 2017 just bitten by this.
https://bitbucket.org/pyglet/pyglet/issues/117/pyglet-produces-spurious-importsReacted by jershellany update on this?
I was just bitten by this when using apache_beam with python3.
To reproduce:
echo "raise NotImplementedError('This test.py file should not be touched')" >> ./test.py pip install apache_beam python -c "import apache_beam as beam"I notice that the comment for
exclude_local_folder_importswhich is called fromimport_top_level_modulesstates:(This was need prior to v0.16.0 because the presence of a configparser folder would otherwise have prevented setuptools from running on Py3. Maybe it's not needed any more?)It seems to work fine without it. Perhaps it's time.
Reacted by Oriol Nieto, Daniel Pasut, Robert Clewley and Julia HaagAlso bitten while using the dash plotting library that relies on this package. I was getting very strange behavior because I happened to have a quick-and-dirty
test.pyfor experimenting with my package during development, that turns out to have been running and silently changing critical state every time I did a local test of my app. I really dislike debugging silent issues like this. Please consider prioritizing the removal of this behavior.Reacted by ftfishShadowing modules names from the standard lib is always going to lead to pain. "test" is a part of the standard lib, future is not in error in expecting it to exist. But users are in error in shadowing its name.
future-version: 0.16.0
python-ver: 3.5
When importing either
future.movesorfuture.backportspackages, it invokesimport_top_level_modules()which attempts to import various modules by name. For instance, if there is atest.pyin user project, it is also gets unexpectedly imported.According the message of one implicated commit 264f9bc, the
import_top_level_modules()method was introduced for "getting the test runner working on travis-ci on Py3".Wouldn't be better to place this code in test-packages?