[issue31741] backports import path can not be overridden in Windows (Linux works fine)

Paul Moore added the comment: Also, one of the packages installed creates a file configparser-3.5.0-py2.7-nspkg.pth This has some very suspicious looking content: import sys, types, os;has_mfs = sys.version_info > (3, 5);p =

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

Zachary Ware added the comment: Note that your instructions start with downloading the installer for 2.7.0, whereas the latest version of 2.7 is 2.7.14, which includes pip. backports is a strange beast of a package, which tries to emulate Python 3's namespace packages

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

Chris Caron added the comment: Just to point out, i forgot the instructions of installing pip (right before) the following entry in my last post: >> ** Heads up >> So at this point, the C:\Python27\Lib\site-packages will contain the >>> >> following: pip, setuptools, and

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

Chris Caron added the comment: -- Download Instructions * 64 Bit ver of Python v2.7 for Windows https://www.python.org/ftp/python/2.7/python-2.7.amd64.msi * Microsoft Visual C++ Compiler for Python 2.7: https://www.microsoft.com/en-ca/download/details.aspx?id=44266. --

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

Paul Moore added the comment: My feeling is still that it's an issue with things (i.e., imports) happening before you adjust sys.path. But without seeing actual code that reproduces the issue, there's no way of being sure. And if that is what's going on, it wouldn't be

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

R. David Murray added the comment: Ah, so backports is a package on pypi. You should report this problem wherever they do their bug tracking. It is *possible* there is some problem in 2.7 on windows, but it is much more likely to be a bug in backports on windows. In

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

Paul Moore added the comment: > I did use `pip` to install packages as you'll see in the screenshot. Sorry, I don't see any pip commands. Please could you include sample commands inline as text, and not as screenshots, as attached files aren't accessible from emails...

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

Chris Caron added the comment: I'm not doing anything unusual. Just to recap, I installed Python27 (in Windows 7 in my case- but this problem happens in Windows 10 too). I did use `pip` to install packages as you'll see in the screenshot. But even if i rename the

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

Change by Chris Caron : Added file: https://bugs.python.org/file47210/Python.Test.zip ___ Python tracker ___

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

Change by Chris Caron : Added file: https://bugs.python.org/file47209/Test.Script.Output.png ___ Python tracker ___

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

Change by Chris Caron : Added file: https://bugs.python.org/file47208/Test.Script.Backports.Dir.png ___ Python tracker ___

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

Change by Chris Caron : Added file: https://bugs.python.org/file47207/Test.Directory.png ___ Python tracker ___

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

Change by Chris Caron : Added file: https://bugs.python.org/file47206/site-packages-Directory.png ___ Python tracker ___

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

Change by Chris Caron : Added file: https://bugs.python.org/file47205/Test.py ___ Python tracker ___

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

Paul Moore added the comment: The "backports" module you refer to as being in site-packages is not shipped with the standard library, it's a 3rd party addon that presumably you installed yourself. You'll need to let us know what you did to install it. You say you

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

R. David Murray added the comment: What is "the backports module"? I still don't understand what a backports directory, that I don't think our installer creates, has to do with your MyLibraries directory. I'm sorry that I'm having trouble following your explanation.

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

Chris Caron added the comment: Thank you for replying so quickly; the issue stems from a bug created here which explains it a bit better: https://github.com/caronc/nzb-notify/issues/27 (scroll to the bottom). In my case, I had a lib\site-packages\backports in C:\Python27

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

R. David Murray added the comment: Where did you get your installer? I don't find any references to 'backports' in our repo, other than a couple of places in the docs where the word appears. I also don't understand the relationship between your MyPackages and a

[issue31741] backports import path can not be overridden in Windows (Linux works fine)

New submission from Chris Caron : The Windows install of Python 2.7.13 defaults it's install into **C:\Python27**. It creates several subdirectories within this; one of which is **C:\Python27\lib\site-packages\backports**. So just out of the box (without this script