Message310345
| Author | vstinner |
|---|---|
| Recipients | barry, martin.panter, mdk, pitrou, twouters, vstinner, xdegaye |
| Date | 2018-01-20.13:22:44 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1516454564.8.0.467229070634.issue32430@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> Because we don't want to maintain more config options? Really, I don't to want to further complicate our build process. I don't see how adding an option to make one path configurable would make the build process more complicated. 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. If I modify it, IMHO it's a configuration file, and it shouldn't be part of Python code base. It's fine to have a default configuration, but if you don't want to use the default, just pass the path to your own config. No? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-01-20 13:22:44 | vstinner | set | recipients: + vstinner, twouters, barry, pitrou, xdegaye, martin.panter, mdk |
| 2018-01-20 13:22:44 | vstinner | set | messageid: <1516454564.8.0.467229070634.issue32430@psf.upfronthosting.co.za> |
| 2018-01-20 13:22:44 | vstinner | link | issue32430 messages |
| 2018-01-20 13:22:44 | vstinner | create | |