On 8/28/07, Lars Gustäbel <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 27, 2007 at 05:16:37PM -0700, Guido van Rossum wrote:
> > As anyone following the py3k checkins should have figured out by now,
> > I'm on a mission to require all code to be consistent about bytes vs.
> > str. For example binary fi
Yes, that makes more sense. Bah, three revisions for one.
On 8/28/07, Bill Janssen <[EMAIL PROTECTED]> wrote:
> > Until ssl.py is fixed, I've added quick hacks to test_ssl.py and
> > test_socket_ssl.py to disable these tests, so people won't be alarmed
> > by the test failures.
>
> You might just
Eric Smith wrote:
> Jim Jewett wrote:
>> but you might want to take inspiration from the "tail" of an
>> elementtree node, and return the field with the literal next to it as
>> a single object.
>>
>> (literal_text, field_name, format_spec, conversion)
>
> I think I like that best.
I impleme
> Until ssl.py is fixed, I've added quick hacks to test_ssl.py and
> test_socket_ssl.py to disable these tests, so people won't be alarmed
> by the test failures.
You might just want to configure out SSL support, or have Lib/ssl.py
raise an ImportError, for the moment.
Bill
__
On 8/28/07, Bill Janssen <[EMAIL PROTECTED]> wrote:
> > > If you can hold off one day before doing the trunk merge, I'm going to
> > > post a fix to the Windows SSL breakage this evening (PDT).
> >
> >
> > Too late, sorry, it's already checked in. You can revert the SSL bits if you
> > want, and ta
> > If you can hold off one day before doing the trunk merge, I'm going to
> > post a fix to the Windows SSL breakage this evening (PDT).
>
>
> Too late, sorry, it's already checked in. You can revert the SSL bits if you
> want, and take care to merge the proper changes later.
No, that's OK. I'
On 8/29/07, Bill Janssen <[EMAIL PROTECTED]> wrote:
> If you can hold off one day before doing the trunk merge, I'm going to
> post a fix to the Windows SSL breakage this evening (PDT).
Too late, sorry, it's already checked in. You can revert the SSL bits if you
want, and take care to merge the
> I'm trying to merge the trunk into the py3k branch (so I can work on
> removing simple slices), but the SSL changes in the trunk are in the way.
> That is to say, the new 'ssl' module depends on the Python 2.x layout in the
> 'socket' module. Specifically, that socket.socket is a wrapper class ar
Jim Jewett wrote:
> On 8/28/07, Eric Smith <[EMAIL PROTECTED]> wrote:
>> parse(format_string)
>
>> ... returns an iterable of tuples
>> (literal_text, field_name, format_spec, conversion)
>
> Which are really either
>
> (literal_text, None, None, None)
> or
> (None, field_name, format_sp
On 8/28/07, Eric Smith <[EMAIL PROTECTED]> wrote:
> parse(format_string)
>... returns an iterable of tuples
> (literal_text, field_name, format_spec, conversion)
Which are really either
(literal_text, None, None, None)
or
(None, field_name, format_spec, conversion)
I can't help thinking
On 8/28/07, Benji York <[EMAIL PROTECTED]> wrote:
> Blake Winton wrote:
> > Raymond Hettinger wrote:
> >>> On Aug 27, 2007, at 6:16 PM, [EMAIL PROTECTED] wrote:
> >> Ask ten of your programmer friends to write down "result equals
> >> object dot get value" ...
> > Sure, but given the rise of Java
I'm trying to merge the trunk into the py3k branch (so I can work on
removing simple slices), but the SSL changes in the trunk are in the way.
That is to say, the new 'ssl' module depends on the Python 2.x layout in the
'socket' module. Specifically, that socket.socket is a wrapper class around
_so
On 8/28/07, Nick Coghlan wrote:
> On the gripping hand, breaking getattr, getitem, setattr, setitem,
> delattr and delitem without a *really* good reason would mean seriously
> annoying a heck of a lot of people for no real gain.
>
Making an exception to the naming convention for builtins seams
Unfortunately, I read nearly all my mailing lists through gmane with nntp
- and gmane is down currently (it doesn't deliver new messages any more).
So I cannot write a reply in the original thread :-(
Neal:
> > We got 'em. Let the spam begin! :-)
> >
> > This page is not linked from the web anyw
Unfortunately, I read nearly all my mailing lists through gmane with nntp
- and gmane is down currently (it doesn't deliver new messages any more).
So I cannot write a reply in the original thread :-(
Neal:
> We got 'em. Let the spam begin! :-)
>
> This page is not linked from the web anywhere:
Eric Smith wrote:
> One of the things that PEP 3101 deliberately under specifies is the
> Formatter class, leaving decisions up to the implementation. Now that a
> working implementation exists, I think it's reasonable to tighten it up.
I should also have included the recipe for the 'smart' f
Thomas Heller schrieb:
> Martin v. Löwis schrieb:
>>> Since the tests fail on the trunk (on the windows machines),
>>> the 'clean' step is not run.
>>
>> No. The 'clean' step is run even if the test step failed.
>>
>> The problem must be somewhere else: for some reason, the
>> connection breaks d
> Since the tests fail on the trunk (on the windows machines),
> the 'clean' step is not run.
No. The 'clean' step is run even if the test step failed.
The problem must be somewhere else: for some reason, the
connection breaks down/times out; this causes the build
to abort.
Can you check the sla
> * Add the branch in the buildbot master.cfg file. 2 places need to be
> updated.
> * Add new rules in the apache default configuration file (2 lines).
> Make sure to use the same port number in both the changes.
> * Check in the buildbot master config. apache config too?
* Edit pydotorg:bu
Unfortunately, I read nearly all my mailing lists through gmane with nntp
- and gmane is down currently (it doesn't deliver new messages any more).
So I cannot write a reply in the original thread :-(
Neal:
> > We got 'em. Let the spam begin! :-)
> >
> > This page is not linked from the web anyw
> It's fairly easy to do - I just have to tell the build slaves to
> build the 3k branch as well. The active branches (2.5, trunk, 3k)
> will then compete for the slaves, in a FIFO manner (assuming there
> are concurrent commits).
Apparently, Neal already did that. The 3k buildbots are at
http://
> Agreed. Neal tried to set up a buildbot on the only machine he can
> easily use for this, but that's the "old gentoo box" where he keeps
> getting signal 32. (I suspect this may be a kernel bug and not our
> fault.) I forget who can set up buildbots -- is it Martin? Can someone
> else help?
It's
On 8/28/07, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> > On Aug 27, 2007, at 6:16 PM, [EMAIL PROTECTED] wrote:
> >
> >> I would like to see PEP 8 remove the "as necessary to improve
> >> readability" in the function and method naming conventions. That
> >> way methods like StringIO.getvalue()
On 8/27/07, Gregory P. Smith <[EMAIL PROTECTED]> wrote:
> I'm sure the BerkeleyDB library is not expecting the data passed in as
> a lookup key to change mid database traversal. No idea if it'll
> handle that gracefully or not but I wouldn't expect it to and bet its
> possible to cause a segfault
I updated the patches destined for the trunk (slice-object support for all
objects that supported simple slicing, and actual extended slicing support
for most of them) and checked them in. Next stop is cleaning up the actual
slice-removal bits. I do have two remaining issues: what do we do about
Py
On 8/28/07, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Benji York wrote:
> > Blake Winton wrote:
> >> On the one hand, I really like consistency in my programming languages.
> >> On the other hand, a foolish consistency is the hobgoblin of little minds.
> >
> > I call quote misapplication. Having p
On 8/28/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> On Aug 27, 2007, at 11:20 PM, Guido van Rossum wrote:
>
> > But I don't see the point of defaulting to raw-unicode-escape --
> > what's the use case for that? I think you should just explicitly say
> > s.encode('raw-unicode-escape') where you n
On 8/27/07, Greg Ewing <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > I think we can't really drop s.encode(), for symmetry with b.decode().
>
> Do we actually need b.decode()?
For symmetry with s.encode().
--
--Guido van Rossum (home page: http://www.python.org/~guido/)
__
Benji York wrote:
> Blake Winton wrote:
>> On the one hand, I really like consistency in my programming languages.
>> On the other hand, a foolish consistency is the hobgoblin of little minds.
>
> I call quote misapplication. Having predictable identifier names isn't
> "foolish". Having to divi
Blake Winton wrote:
> Raymond Hettinger wrote:
>>> On Aug 27, 2007, at 6:16 PM, [EMAIL PROTECTED] wrote:
I would like to see PEP 8 remove the "as necessary to improve
readability" in the function and method naming conventions. That
way methods like StringIO.getvalue() can be renamed
Raymond Hettinger wrote:
>> On Aug 27, 2007, at 6:16 PM, [EMAIL PROTECTED] wrote:
>>> I would like to see PEP 8 remove the "as necessary to improve
>>> readability" in the function and method naming conventions. That
>>> way methods like StringIO.getvalue() can be renamed to
>>> StringIO.get_value
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 27, 2007, at 11:22 PM, Guido van Rossum wrote:
> On 8/27/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>>
>> On Aug 27, 2007, at 6:16 PM, [EMAIL PROTECTED] wrote:
>>
>>> I would like to see PEP 8 remove the "as necessary to improve
>>> readabilit
One of the things that PEP 3101 deliberately under specifies is the
Formatter class, leaving decisions up to the implementation. Now that a
working implementation exists, I think it's reasonable to tighten it up.
I have checked in a Formatter class that specifies the following methods
(in addi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 27, 2007, at 11:20 PM, Guido van Rossum wrote:
> But I don't see the point of defaulting to raw-unicode-escape --
> what's the use case for that? I think you should just explicitly say
> s.encode('raw-unicode-escape') where you need that. Any r
Neal Norwitz wrote:
> There are several other known warnings on various platforms:
...
> Python/../Objects/stringlib/unicodedefs.h:26: warning: 'STRINGLIB_CMP'
> defined but not used
I fixed this warning in r57613. Unfortunately I had to change from an
inline function to a macro, but I don't see
> On Aug 27, 2007, at 6:16 PM, [EMAIL PROTECTED] wrote:
>
>> I would like to see PEP 8 remove the "as necessary to improve
>> readability" in the function and method naming conventions. That
>> way methods like StringIO.getvalue() can be renamed to
>> StringIO.get_value().
Gratuitous breakage --
On Mon, Aug 27, 2007 at 05:16:37PM -0700, Guido van Rossum wrote:
> As anyone following the py3k checkins should have figured out by now,
> I'm on a mission to require all code to be consistent about bytes vs.
> str. For example binary files will soon refuse str arguments to
> write(), and vice ver
We got 'em. Let the spam begin! :-)
This page is not linked from the web anywhere:
http://python.org/dev/buildbot/3.0/
I'm not expecting a lot of signal out of them at the beginning. All
but one has successfully compiled py3k though. I noticed there were
many warnings on windows. I wonder i
Talin wrote:
> I know that Greg Ewing was working on a "minimal" python GUI
> (http://www.cosc.canterbury.ac.nz/greg.ewing/python_gui/), but it hasn't
> been updated in over a year. And I'm not sure that a minimal toolkit is
> really all that useful.
Don't worry, I haven't given up! And I plan
39 matches
Mail list logo
