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
python setup.py picks prefix from ~/.pydistutils.cfg #9536
Comments
Patch for sage-main |
comment:1
Attachment: setup_py_issue.patch.gz |
comment:2
The following packages from the distribution use setup.py and may be affected:
The following already have setup.cfg, but it may not have the prefix definition:
|
comment:3
Hi! Cheers, |
comment:4
Hi Michael, Best regards, |
comment:5
maybe, I did not try (just read the docs): create system distutils.cfg
|
comment:6
Hi, Regards, |
patch for sage/spkg/base/sage-env sage/local/bin/sage-env (needs python 2.6.4.p10) |
comment:7
Attachment: sage-env.patch.gz Hi, The new spkg can be found here: The last patch adds this variable to Regards, |
comment:8
Reported upstream: |
Changed upstream from Not yet reported upstream; Will do shortly. to Reported upstream. Little or no feedback. |
comment:9
Minor update: http://sage.math.washington.edu/home/dreyer/suse101/python-2.6.4.p10.spkg (useful, if the |
comment:10
Replying to @alexanderdreyer:
You should also create patches/ACKS.txt.diff as a unified diff file. Although its fairly obvious you can recreate that now, that will not be the case if Python source code is updated. Would a simpler solution not be for sage-env to set this variable and export it? I don't know much about python, so can't review this myself. Dave |
comment:11
Maybe a misunderstanding: the patch of python is necessary to fix that issue anyway. (This first variant didn't work, if the environment variable was not set.) |
Attachment: python-2.6.4.p10.patch.gz Adding handling of environment variable DISTUTILS_NO_USER_CFG to python's distutils |
comment:12
I've added ACKS.txt.patch to the spkg. |
comment:14
The python community does not like the idea of adding an environment variable, see: |
Changed upstream from Reported upstream. Little or no feedback. to Reported upstream. Developers deny it's a bug. |
comment:16
Please fill in your real name as Author. |
comment:28
|
comment:29
I've created an upstream issue for this: |
comment:30
That's annoying. For now we should probably remove pip install from pyzmq. |
Dependencies: #21835 |
comment:31
Upstream pyzmq reports that it works with pip 9.0.1, setuptools 28.8.0. Let's try with upgrading these packages. #21835 does the upgrade of pip to 9.0.0... |
comment:32
Upgrading setuptools to 28.8.0 does not fix the pyzmq install. I'll wait for the pip upgrade. |
Changed branch from |
Commit: |
comment:35
Here's a fix for our |
Changed dependencies from #21835 to none |
comment:37
Just a comment: it would make sense to use |
comment:38
I agree, but that should be on a different ticket. I've created #21864 for this. |
comment:39
Needs review. |
comment:41
Rebased, needs review. |
comment:42
ping? |
comment:43
The issue with |
Changed branch from u/mkoeppe/6dcaebb5f95abdc78cce729bcced7dc96ee5cb1f to |
Hi,
several packages do use
python setup.py
. This picks up the customized settings from ~/.pydistutils.cfg. This is bad, because it overrides the prefix setting.For sage-main, I'll attach a patch:
setup.cfg
in the corresponding directory overrides the usere settings. Maybe there's a global solution.Regards,
Alexander Dreyer
......
Update for Sage 7.5. The problem reported on this ancient ticket is still present and affects
setup.py
It can be tested by creating the following
~/.pydistutils.cfg
:The patch on the ticket uses
pip --isolated
andsetup.py --no-user-cfg
Note there appear to be some issues regarding these option with early versions of Python 3.x: pypa/pip#3509
Upstream: Reported upstream. Developers deny it's a bug.
CC: @jdemeyer @embray @nexttime @kiwifb @vbraun
Component: build
Author: Matthias Koeppe
Branch/Commit:
375faba
Reviewer: Erik Bray
Issue created by migration from https://trac.sagemath.org/ticket/9536
The text was updated successfully, but these errors were encountered: