You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/usr/lib/python2.7/dist-packages/pkg_resources.py:1049: UserWarning: /home/USER/.python-eggs is writable by group/others and vulnerable to attack when used with get_resource_filename. Consider a more secure location (set with .set_extraction_path or the PYTHON_EGG_CACHE environment variable).
warnings.warn(msg, UserWarning)
I'm not sure why a warning would kill the run it and I haven't found the call in the script, but after modifying the folder ($ chmod g-wx,o-wx ~/.python-eggs), it completes satisfactorily.
Perhaps this could be modified to warn the user rather than terminate the process, as I can't imagine it is process breaking.
The text was updated successfully, but these errors were encountered:
/usr/lib/python2.7/dist-packages/pkg_resources.py:1049: UserWarning: /home/USER/.python-eggs is writable by group/others and vulnerable to attack when used with get_resource_filename. Consider a more secure location (set with .set_extraction_path or the PYTHON_EGG_CACHE environment variable).
warnings.warn(msg, UserWarning)
I'm not sure why a warning would kill the run it and I haven't found the
call in the script, but after modifying the folder ($ chmod g-wx,o-wx
~/.python-eggs), it completes satisfactorily.
Perhaps this could be modified to warn the user rather than terminate the
process, as I can't imagine it is process breaking.
From what I can tell that's a problem with the permissions on that machine
my setup.py doesn't touch that directly. I could be wrong, but as of now
I don't know how I could fix this from my end.
I found my runs always failing with this warning:
I'm not sure why a warning would kill the run it and I haven't found the call in the script, but after modifying the folder (
$ chmod g-wx,o-wx ~/.python-eggs
), it completes satisfactorily.Perhaps this could be modified to warn the user rather than terminate the process, as I can't imagine it is process breaking.
The text was updated successfully, but these errors were encountered: