Message 310346 - Python tracker

➜

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	pitrou
Recipients	barry, martin.panter, mdk, pitrou, twouters, vstinner, xdegaye
Date	2018-01-20.13:25:19
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<fee5ac0d-c647-e8dd-bcc3-5c4dae39464d@free.fr>
In-reply-to	<1516454564.8.0.467229070634.issue32430@psf.upfronthosting.co.za>

Content
Le 20/01/2018 à 14:22, STINNER Victor a écrit : > > I don't see how adding an option to make one path configurable would make the build process more complicated. Do you think implementing and maintaing an option has no cost? > It seems like Xavier and Thomas do use Modules/Setup for their need, and for me it's strange to have to modify Modules/Setup (or Modules/Setup.dist) if it's tracked by Git. Distributors routinely modify files that are tracked by git. Modules/Setup doesn't have to be an exception. See Anaconda example I posted above. Also you can look up packaging by RedHat or any other distro.

Le 20/01/2018 à 14:22, STINNER Victor a écrit :
> 
> I don't see how adding an option to make one path configurable would make the build process more complicated.

Do you think implementing and maintaing an option has no cost?

> It seems like Xavier and Thomas do use Modules/Setup for their need, and for me it's strange to have to modify Modules/Setup (or Modules/Setup.dist) if it's tracked by Git.

Distributors routinely modify files that are tracked by git.
Modules/Setup doesn't have to be an exception.

See Anaconda example I posted above.  Also you can look up packaging by
RedHat or any other distro.

History
Date	User	Action	Args
2018-01-20 13:25:19	pitrou	set	recipients: + pitrou, twouters, barry, vstinner, xdegaye, martin.panter, mdk
2018-01-20 13:25:19	pitrou	link	issue32430 messages
2018-01-20 13:25:19	pitrou	create