-
Notifications
You must be signed in to change notification settings - Fork 9
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
project toml broke editable install with pip 19.1 #7
Comments
Original comment by T La (Bitbucket: 5c73c2a3cfbc206be909a286, ).
|
Original comment by T La (Bitbucket: 5c73c2a3cfbc206be909a286, ). For some reason, I couldn’t replicate the issue: I uninstalled cogent3 and numpy. My pip version is 19.1.1 (may try upgrade to that version on your end?) Then I sucessfully installed. I did remember reading something about an older pip version (possibly 19.1) having this sort of problem, so that could be the cause of this bug. Let me know how it goes. |
Original comment by GavinH (Bitbucket: 557058:e40c23e1-e273-4527-a2f8-5de5876e870d, ). direct installation via pip worked for me too, but install via conda did not.
fails at the last step |
Original comment by T La (Bitbucket: 5c73c2a3cfbc206be909a286, ). Thats supposed to be an
switch right? |
Original comment by T La (Bitbucket: 5c73c2a3cfbc206be909a286, ). I ran the following and successfully installed the conda environment.
Can I see the output logs please? |
Original comment by GavinH (Bitbucket: 557058:e40c23e1-e273-4527-a2f8-5de5876e870d, ). post test.yml here please |
Original comment by T La (Bitbucket: 5c73c2a3cfbc206be909a286, ).
|
Original comment by T La (Bitbucket: 5c73c2a3cfbc206be909a286, ). Was the ticket regarding the original yaml with all dev tools? |
Original comment by T La (Bitbucket: 5c73c2a3cfbc206be909a286, ). Actually, I think I’ve got it replicated. Is this what your output looks like?
|
Original comment by GavinH (Bitbucket: 557058:e40c23e1-e273-4527-a2f8-5de5876e870d, ). That’s the one! |
Original comment by T La (Bitbucket: 5c73c2a3cfbc206be909a286, ). Great! I’ll tackle it when I get a chance tomorrow. |
Original comment by T La (Bitbucket: 5c73c2a3cfbc206be909a286, ). From all the articles/git forums I’ve been reading, this issue isn’t an uncommon one. I just stumbled on a potential fix, so I’ll give it a try and see how it goes. |
Original comment by T La (Bitbucket: 5c73c2a3cfbc206be909a286, ). Can I double check that you are using pip 19.1? The solution won’t work for older versions as I just found out… 😞 |
Original comment by T La (Bitbucket: 5c73c2a3cfbc206be909a286, ). Actually, even worse: pypa/pip#6447 The pull request that is supposed to fix this problem isn’t merged yet. |
Original comment by T La (Bitbucket: 5c73c2a3cfbc206be909a286, ). So we are actually playing with bleeding edge stuff, and boy, keeping up with Python is harder than keeping up with the Jones. There are development versions of pip which claim to fix the issue, but I haven’t had any luck, nor do I think you want us to force users to install development versions of pip. As it stands currently, this is a bug in pip that is not yet resolved. We could revoke the toml while we wait for the upstream issue to be fixed, but its your call. Where to now? |
Original comment by GavinH (Bitbucket: 557058:e40c23e1-e273-4527-a2f8-5de5876e870d, ). Thanks for the research. Since this only affects developers, we just enforce pip version 18 (as I have in the revised conda environment file) until there’s a proper fix. Putting this Issue on hold until there's a proper fix to pip. |
Original report by GavinH (Bitbucket: 557058:e40c23e1-e273-4527-a2f8-5de5876e870d, ).
When you have pip 19.1 installed, I get error messages that indicates cogent3 cannot be installed in editable mode and use
--no-use-pep517
but I cannot get that to workPlease see if you can reproduce and then fix!
The text was updated successfully, but these errors were encountered: