-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
markupsafe silently failing on amazon linux #836
Comments
Hmm, I couldn't reproduce locally. Tested with both a Python 2 & 3 virtualenv.
|
Ivoz, can you confirm that that was running on Amazon Linux? |
@dsadinoff This looks like something specific to Amazon Linux. And markupsafe's I suspect markupsafe's |
here you go:
|
Bah. That still didn't show the output of |
I just ran locally on ArchLinux. It's actually surprising that pip installed markupsafe twice, from your initial paste. It should normally say that the requirement is already satisfied. |
It is reproducible on amazon linux 2015.09 where I encountered same problem installing twisted, see my comment on SO. Amazon Linux installs virtualenv-12.0.7 by default, I fixed it by installing latest 15.0.0. |
I was able to solve this by using the 64bit Amazon Linux 2016.03 v2.1.0 AMI. Also, since I had replaced the default wsgi.conf with one that I made changes to, it was critical that I got the original wsgi.conf for this AMI and made my customizations to it rather than continuing to use the customized wsgi.conf that I was using for the previous AMI. |
Same for me, upgrading virtualenv from 12.0.7 to 15.0.0 did the trick. @pfmoore
|
Looks like an old version of pip, as it's doing I'd be inclined to write this off as a quirk of old behaviour of "something" (pip, setuptools?) and say that upgrading is the fix, unless anyone hits it with a current version of pip. |
Agree, virtualenv 12.07 uses pip 6.0.8 and virtualenv 15.1.0 uses pip 9.0.1 |
Yup, looks fine for me now as well. looks like the various tools "grew out" of the bug. thanks! |
We're still getting this same issue on Amazon Linux for MarkupSafe. Any workaround? |
I'm seeing this on several compiled extensions on AmazonLinux 2.8.0, so I don't think that this is specific to markupsafe. See here for workaround: #1117 (comment) |
[cross-posted from SO: http://stackoverflow.com/questions/34554471/markupsafe-wont-install-in-virtualenv-on-amazon-linux ]
I find that MarkupSafe installs fine in the main machine environment, but in a virutalenv, pip silently fails.
Is there more I ought to do to help debug this?
The text was updated successfully, but these errors were encountered: