This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author prlw1
Recipients Arfrever, barry, dmalcolm, loewis, pitrou, prlw1
Date 2013-05-18.20:34:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368909247.18.0.3947171462.issue17975@psf.upfronthosting.co.za>
In-reply-to
Content
No, I don't think you should close this, as you haven't explained what it is that you won't do.

I think that a sensible plan is to introduce a configure flag whose effect is to not install the files which cause the conflict. You set the default to always install the conflicting files, so the standard install of python gets to be the PY3LIBRARY. What this buys you, is that then you can also install another version of python 3 concurrently and easily.

I just need to find a round tuit to write it...
History
Date User Action Args
2013-05-18 20:34:07prlw1setrecipients: + prlw1, loewis, barry, pitrou, Arfrever, dmalcolm
2013-05-18 20:34:07prlw1setmessageid: <1368909247.18.0.3947171462.issue17975@psf.upfronthosting.co.za>
2013-05-18 20:34:07prlw1linkissue17975 messages
2013-05-18 20:34:06prlw1create