-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'_NamespacePath' object has no attribute 'sort' #45
Comments
The Travis CI environment prepares a test environment with the most recent version of pip available (v9.0.1); however, using this version results in the following error [1]: AttributeError: '_NamespacePath' object has no attribute 'sort' Adjusting the tox requirements to forcefully update pip to the newest version for the interim. When pip v9.0.2+ is available, this commit can be reverted. [1]: #45 Signed-off-by: James Knight <james.d.knight@live.com>
This issue has been addressed on For user's experiencing the same issue in their environment, it is recommended to update their |
/home/travis/build/tonybaloney/sphinxcontrib-confluencebuilder/.tox/py35/lib/python3.5/site-packages/pip/_vendor/pkg_resources/__init__.py fix line 2121 as below. |
@YB-Park Thanks a lot, your solution really works for me! |
The most recent version of Travis CI's Python build [1] appears to no longer require a force update of the pip command line [2]. Tested with image 'travisci/ci-garnet:packer-1512502276-986baf0'. [1]: https://docs.travis-ci.com/user/common-build-problems/#Troubleshooting-Locally-in-a-Docker-Image [2]: #45 Signed-off-by: James Knight <james.d.knight@live.com>
YB-Park |
Removes the custom Python path explicitly set in the tox configuration file. This should resolve situations [1] where pip may not install required packages (and dependencies) into target virtualenv since they are already provided in PYTHONPATH (see also [2]). [1]: #45 [2]: tox-dev/tox#330 Signed-off-by: James Knight <james.d.knight@live.com>
With an environment correction [1], there is no need to forcefully upgrade pip to the most recent development snapshot [2]. Tested with image 'travisci/ci-garnet:packer-1512502276-986baf0' [3]. [1]: e88ef73 [2]: #45 [3]: https://docs.travis-ci.com/user/common-build-problems/#Troubleshooting-Locally-in-a-Docker-Image Signed-off-by: James Knight <james.d.knight@live.com>
Thank you YB_Park, that helped me so much. I have no idea though why that issue came up today, even though yesterday it worked just fine! |
Thanks YB_Park. That line fix really should be incorportated into the next master build. suggest line 2121 be changed to: try: |
Thanks YB_Park. You made my day! |
The automated build does not work. The py35 build fails with the following (ex. job 267816857):
I suspect that this problem is not really with the current source of this extension, but rather an issue with
pip
and/or the tox configuration being used. Using a more recent version pip and setuptools shows that the tox build works; however, I can't seem to get it to work with Travis CI (I haven't had that much experience with using it).I believe the following bug covers of the reason why, but I'm not 100% sure how to apply the workaround changes for the current automated build process:
I was hoping a pip v9.0.2 update would fix this, but I'm not sure when an update will ever be released.
The text was updated successfully, but these errors were encountered: