Amaury Forgeot d'Arc schrieb:
> Ralf Schmitt wrote:
>>
>> On Thu, Mar 20, 2008 at 1:30 PM, Lennart Regebro <[EMAIL PROTECTED]> wrote:
>> >
>> > On Thu, Mar 20, 2008 at 1:16 PM, "Martin v. Löwis" <[EMAIL PROTECTED]>
>> wrote:
>> > > However, it *is* common to install Python code before running it.
Martin v. Löwis schrieb:
>>> It was proposed before, I don't know whether any implementation
>>> on that has started.
>>
>> I don't see anything in the bug tracker. I'd be willing to look at it,
>> if this is what we want to do.
>
> Neither could I. I vaguely remember having people mention it,
On Fri, Mar 21, 2008 at 1:42 AM, Jeroen Ruigrok van der Werven
<[EMAIL PROTECTED]> wrote:
> (To provide counterweight.)
>
>
> -On [20080320 20:44], Barry Warsaw ([EMAIL PROTECTED]) wrote:
> >We have not made a decision to move to Bazaar officially, nor have we made
> >a decision to even move off
On Thu, Mar 20, 2008 at 2:42 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I'm happy to announce that we now have available for public
> consumption, the Python source code for 2.5, 2.6 and 3.0 available
> under the Bazaar distributed version con
On Thu, Mar 20, 2008 at 2:49 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Barry Warsaw schrieb:
>
> > I'm happy to announce that we now have available for public
> > consumption, the Python source code for 2.5, 2.6 and 3.0 available
> > under the Bazaar distributed version control system.
>
> See http://dev.pocoo.org/hg/sandbox/file/tip/auto2to3.py - it's awfully
> slow.
When David Wolever checks in his latest changes, it won't be that
awfully slow anymore.
Regards,
Martin
___
Python-3000 mailing list
[email protected]
http://mail.
>> Neither could I. I vaguely remember having people mention it, but
>> could not find anything, either. Perhaps you need to get
>> approval/agreement first in a separate thread.
>
> Doesn't the code for the -U flag do exactly this?
Not exactly. The future import does it on a per-module basis;
th
On 21/03/2008, Brett Cannon <[EMAIL PROTECTED]> wrote:
> Just to head this off, this is not a specific vote of confidence for
> Bazaar. The Bazaar developers were at PyCon and both Barry and Thomas
> were willing to put the time and effort to get the mirror up and going
> while the Bazaar team w
On Fri, Mar 21, 2008 at 4:28 PM, Paul Moore <[EMAIL PROTECTED]> wrote:
> On 21/03/2008, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > Just to head this off, this is not a specific vote of confidence for
> > Bazaar. The Bazaar developers were at PyCon and both Barry and Thomas
> > were willing to p
On 21/03/2008, Benjamin Peterson <[EMAIL PROTECTED]> wrote:
> I tend to make a repository and make a working copy for each patch in it.
> The history is saved in the repository so it's efficient.
OK, so just lots of copies, fair enough. Presumably just use bzr diff
to create patches? Much like Sub
On Fri, Mar 21, 2008 at 5:04 PM, Paul Moore <[EMAIL PROTECTED]> wrote:
> On 21/03/2008, Benjamin Peterson <[EMAIL PROTECTED]> wrote:
> > I tend to make a repository and make a working copy for each patch in
> it.
> > The history is saved in the repository so it's efficient.
>
> OK, so just lots of
On Fri, Mar 21, 2008 at 3:10 PM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
>
>
>
>
> On Fri, Mar 21, 2008 at 5:04 PM, Paul Moore <[EMAIL PROTECTED]> wrote:
> >
> > On 21/03/2008, Benjamin Peterson <[EMAIL PROTECTED]> wrote:
> > > I tend to make a repository and make a working copy for each patch
On Fri, Mar 21, 2008 at 6:12 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 21, 2008 at 3:10 PM, Benjamin Peterson
> <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > On Fri, Mar 21, 2008 at 5:04 PM, Paul Moore <[EMAIL PROTECTED]> wrote:
> > >
> > > On 21/03/2008, Benjamin Peterson <[EMAIL
I think Python needs a dedicated "pragma" syntax; we already have two
pragma syntaxes ("from __future__ import" and "# coding"), and I think a
syntax designed for expressing pragmas would be much clearer than using
existing language features in weird ways to express pragmas. But that's
a deb
Guido van Rossum schrieb:
> Even though the more popular PyInt_ APIs are still available (even if
> only as macros).
THe PyInt_* macros are only available when Include/intobject.h is
included explicitly. It's not in Python.h any more.
> I disagree. Bad merges are already a frequent cause of insta
On Fri, Mar 21, 2008 at 6:26 PM, Larry Hastings <[EMAIL PROTECTED]> wrote:
>
>
> I think Python needs a dedicated "pragma" syntax; we already have two
> pragma syntaxes ("from __future__ import" and "# coding"), and I think a
> syntax designed for expressing pragmas would be much clearer than usin
> I think Python needs a dedicated "pragma" syntax; we already have two
> pragma syntaxes ("from __future__ import" and "# coding"), and I think a
> syntax designed for expressing pragmas would be much clearer than using
> existing language features in weird ways to express pragmas. But that's
I hate bringing up something that has been hashed over so many times,
but I'm a bear
of little brain and am not understanding the migration path. The
whole use of the "2to3"
tools seems like an abrupt hack. It is workable, but causes a serious
plan for near term
2.x to 3.x migration. I'd like t
On Fri, Mar 21, 2008 at 4:41 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Guido van Rossum schrieb:
>
> > Even though the more popular PyInt_ APIs are still available (even if
> > only as macros).
>
> THe PyInt_* macros are only available when Include/intobject.h is
> included explicitly. I
On Sat, 22 Mar 2008 00:51:48 +0100, Martin v. Löwis wrote:
>> I think Python needs a dedicated "pragma" syntax; we already have two
>> pragma syntaxes ("from __future__ import" and "# coding"), and I think
>> a syntax designed for expressing pragmas would be much clearer than
>> using existing lan
20 matches
Mail list logo
