On 12/13/2012 1:06 AM, Lennart Regebro wrote:
On Thu, Dec 13, 2012 at 2:24 AM, Terry Reedy wrote:
Or ask the user where to put it.
If we ask where it should be installed, then we need a registry
setting for that
Right.
So I think that asking is not an option at all. It either goes in
%PRO
On 12/12/2012 11:32 PM, Janzert wrote:
On 12/13/2012 1:39 AM, Glenn Linderman wrote:
On 12/12/2012 6:10 PM, Janzert wrote:
On 12/12/2012 8:43 PM, Glenn Linderman wrote:
On 12/12/2012 5:36 PM, Brian Curtin wrote:
>> C:\ProgramData\Python
^ That. Is not the path that the link be
On Thu, Dec 13, 2012 at 9:22 AM, Terry Reedy wrote:
> On 12/13/2012 1:06 AM, Lennart Regebro wrote:
>> All in all I would say I would prefer to install this per Python.
>
> Then explicit update requires multiple downloads or copying. This is a
> violation of DRY. If if is not too large, it would n
Le Thu, 13 Dec 2012 10:07:34 +0100,
Lennart Regebro a écrit :
> On Thu, Dec 13, 2012 at 9:22 AM, Terry Reedy wrote:
> > On 12/13/2012 1:06 AM, Lennart Regebro wrote:
> >> All in all I would say I would prefer to install this per Python.
> >
> > Then explicit update requires multiple downloads or
Am 13.12.2012 10:07, schrieb Lennart Regebro:
> Yes, but this is no different that if you want to keep any library
> updated over multiple Python versions. And I don't want to invent
> another installation procedure that works for just this, or have a
> little script that checks periodically for up
2012/12/13 Antoine Pitrou :
> On Thu, 13 Dec 2012 04:24:54 +0100 (CET)
> benjamin.peterson wrote:
>> http://hg.python.org/cpython/rev/5435a9278028
>> changeset: 80834:5435a9278028
>> user:Benjamin Peterson
>> date:Wed Dec 12 22:24:47 2012 -0500
>> summary:
>> expose TCP_FASTOP
On 12/13/2012 4:07 AM, Lennart Regebro wrote:
On Thu, Dec 13, 2012 at 9:22 AM, Terry Reedy wrote:
On 12/13/2012 1:06 AM, Lennart Regebro wrote:
All in all I would say I would prefer to install this per Python.
Then explicit update requires multiple downloads or copying. This is a
violation o
The default version shown on http://docs.python.org/ is now 3.3.0,
which I think is a Good Thing. However, http://python.org/download/
puts 2.7 first, and says:
"""If you don't know which version to use, start with Python 2.7; more
existing third party software is compatible with Python 2 than Pyt
On Fri, Dec 14, 2012 at 07:57:52AM +1100, Chris Angelico wrote:
> The default version shown on http://docs.python.org/ is now 3.3.0,
> which I think is a Good Thing. However, http://python.org/download/
> puts 2.7 first, and says:
>
> """If you don't know which version to use, start with Python 2.
I'll have a look into distutils2, I tough it was (another) dead end.
I every case my target is py2k (2.7.x) and I've no case for
transitioning to py3k (too much risk).
Lennart Regebro wrote:
On Mon, Dec 10, 2012 at 8:22 AM, Antonio Cavallo
wrote:
Hi,
I wonder if is it worth/if there is a
On Fri, Dec 14, 2012 at 10:10 AM, Antonio Cavallo
wrote:
> I'll have a look into distutils2, I tough it was (another) dead end.
> I every case my target is py2k (2.7.x) and I've no case for transitioning
> to py3k (too much risk).
distutils2 started as a copy of distutils, so it's hard to tell t
Scenario: I'm working on a change that I want to actively test on a
bunch of Snakebite hosts. Getting the change working is going to be
an iterative process -- lots of small commits trying to attack the
problem one little bit at a time.
Eventually I'll get to a point where I'm
On 12/13/2012 05:21 PM, Trent Nelson wrote:
Thoughts?
% hg help rebase
//arry/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/
On Fri, Dec 14, 2012 at 12:02 PM, Larry Hastings wrote:
> On 12/13/2012 05:21 PM, Trent Nelson wrote:
>
> Thoughts?
>
>
> % hg help rebase
>
And also the histedit extension (analagous to "git rebase -i").
Both Git and Hg recognise there is a difference between interim commits and
ones you
On Thu, Dec 13, 2012 at 1:57 PM, Chris Angelico wrote:
> The default version shown on http://docs.python.org/ is now 3.3.0,
> which I think is a Good Thing. However, http://python.org/download/
> puts 2.7 first, and says:
>
> """If you don't know which version to use, start with Python 2.7; more
>
On Thu, 13 Dec 2012 20:21:24 -0500, Trent Nelson wrote:
> - Use a completely separate clone to house all the intermediate
> commits, then generate a diff once the final commit is ready,
> then apply that diff to the main cpython repo, then push that.
> This ap
On Thu, Dec 13, 2012 at 6:48 PM, R. David Murray wrote:
> On Thu, 13 Dec 2012 20:21:24 -0500, Trent Nelson wrote:
>> - Use a completely separate clone to house all the intermediate
>> commits, then generate a diff once the final commit is ready,
>> then apply that diff
On Dec 14, 2012, at 12:36 PM, Nick Coghlan wrote:
>Both Git and Hg recognise there is a difference between interim commits and
>ones you want to publish and provide tools to revise a series of commits
>into a simpler set for publication to an official repo.
One of the things I love about Bazaar i
In article <20121214024824.3bccc250...@webabinitio.net>,
"R. David Murray" wrote:
> On Thu, 13 Dec 2012 20:21:24 -0500, Trent Nelson wrote:
> > - Use a completely separate clone to house all the intermediate
> > commits, then generate a diff once the final commit is ready,
> >
R. David Murray writes:
> those commits...if you don't want those intermediate commits in the
> official repo, then why is a diff/patch a bad way to achieve that?
Because a decent VCS provides TOOWTDI. And sometimes there are
different degrees of "intermediate", or pehaps you even want to slic
On Mon, Dec 10, 2012 at 11:16 PM, Antoine Pitrou wrote:
> On Tue, 11 Dec 2012 03:05:19 +0100 (CET)
> gregory.p.smith wrote:
> > Using 'long double' to force this structure to be worst case aligned
> is no
> > longer required as of Python 2.5+ when the gc_refs changed from an int (4
> > bytes) t
On Thu, Dec 13, 2012 at 11:27 PM, Gregory P. Smith wrote:
>
> On Mon, Dec 10, 2012 at 11:16 PM, Antoine Pitrou wrote:
>
>> On Tue, 11 Dec 2012 03:05:19 +0100 (CET)
>> gregory.p.smith wrote:
>> > Using 'long double' to force this structure to be worst case aligned
>> is no
>> > longer required
On Mon, Dec 10, 2012 at 11:21 PM, Antoine Pitrou wrote:
> On Tue, 11 Dec 2012 08:16:27 +0100
> Antoine Pitrou wrote:
>
> > On Tue, 11 Dec 2012 03:05:19 +0100 (CET)
> > gregory.p.smith wrote:
> > > Using 'long double' to force this structure to be worst case aligned
> is no
> > > longer require
23 matches
Mail list logo
