Glenn Linderman <v+pyt...@g.nevcal.com> added the comment: msg156410 sounds good to me... +1
If the conversion is optional in 3.3, that would seem to solve the problem; if BinaryDir is added, people can use that for 3.3; if people want to use software that hasn't migrated yet, they choose the default path of least resistance, leaving things where they are but with BinaryDir pointing there. PATH manipulations would be simpler, being a single PATH entry, so tying that to choosing the non-default option seems practical. This would allow people that don't need the compatibility with installers that don't understand the new structure, to continue to function, gives the installer people a test bed if they don't get things done by the time 3.3 ships, gives people that prefer the consistency across platform structures the ability to have it, as long as they don't need the intsaller... in short, one question at install time could allow us to have our cake and eat it too! Clearly the launcher may need some adjustments for this, but BinaryDir should suffice to help it do the right thing for both types of installation. ---------- nosy: +v+python _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14302> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
