Mark, MAL, Martin, Tarek,
Could you comment on this?
This is in the context of changing the name of the 'Scripts' directory
on windows to 'bin'. Éric brings up the point (explained more below)
that if we make this change, packages made/installed the new packaging
infrastructure and those made/
On 3/20/2012 3:31 PM, Paul Moore wrote:
> Serious question: Given a brand new PC, if you were installing Python
> 2.7, 3.2, 3.3a1, jython, and pypy, what would you do (beyond simply
> running 5 installers) to get your environment set up the way you want?
I install each python in its own directory:
On 3/20/2012 1:19 PM, Paul Moore wrote:
> Somewhat. I don't really object to #1, but mildly object to #2. I also
> note that the proposals round the Lib directory seem to have
> disappeared. I assume those have been dropped - they were the ones I
> did object to.
They are of secondary importance t
On 3/20/2012 5:48 AM, Mark Hammond wrote:
> While I'm still unclear on the actual benefits of this, Martin's
> approach strikes a reasonable compromise so I withdraw my objections.
Ok. I was out of town and so could not respond to most of the latest
discussion.
A question for you Mark, Paul, (a
On 3/16/2012 11:57 AM, Glenn Linderman wrote:
> So I think I'm finally beginning to see the underlying reason why Van is
> desiring this consistency: It is not that he wants to check in his
> installation of Python, but that he wants to check in his installation
> of his packages and scripts into
On 3/16/2012 10:53 AM, Paul Moore wrote:
> The only way I can read this to make sense is that you somehow
> consider the Python installation as part of your development
> environment (you mentioned source control earlier in the thread -
> surely you don't manage your Python installation in source c
On 3/16/2012 3:38 AM, Paul Moore wrote:
> On 16 March 2012 00:12, Carl Meyer wrote:
>> Changing the directory name is in fact a new and different (and much
>> more invasive) special case, because distutils et al install scripts
>> there, and that directory name is part of the distutils install sch
Carl -
> Changing the directory name is in fact a new and different (and much
> more invasive) special case, because distutils et al install scripts
> there, and that directory name is part of the distutils install scheme.
> Installers don't care where the Python binary is located, so moving it
>
