Message161530
2. Yes, only the installation directory, because that's the only directory we create. Scripts is created by distutils/packaging, but perhaps we could add it since it is widely used. Anyone have an opinion?
3. Do you have a reason? Many tools that offer path manipulation do not do so by default because it changes how the system operates. If we put this on by default, it will change how a lot of scripts are executed without people expecting it. It's easy to click through an installer like Python's because it's not flashy and there aren't a lot of options as it is. If we just let people click through, things are going to break a lot more than if we make people ask for it.
I could see it becoming a default in a future release once it has been in the wild for a while, but I think we're going to run into a lot of problems if we just flip it right away. |
|
Date |
User |
Action |
Args |
2012-05-24 21:28:14 | brian.curtin | set | recipients:
+ brian.curtin, loewis, ncoghlan, pitrou, giampaolo.rodola, christian.heimes, eric.araujo, jasonspiro, lambacck, srid, jonathan.hartley, pekka.klarck, python-dev, AaronR, jdigital, Jim.Jewett, helder-magalhaes |
2012-05-24 21:28:14 | brian.curtin | set | messageid: <1337894894.42.0.8090744754.issue3561@psf.upfronthosting.co.za> |
2012-05-24 21:28:13 | brian.curtin | link | issue3561 messages |
2012-05-24 21:28:13 | brian.curtin | create | |
|