On Sun, May 25, 2008 at 6:25 AM, Jesus Cea <[EMAIL PROTECTED]> wrote:
> Since I need to port bsddb3 to py3k, what I need to know?. Is any
> *updated* document out there?.
No, but there is a not yet complete, but quite updated set of examples.
http://code.google.com/p/python-incompatibility/
This
>> If the 3.0 API of a module is going to involve breakage which
>> requires authors to update their applications wouldn't this be a good
>> time to PEP-8-ify the module? (Not suggesting that threading would
>> fall into this category.)
Nick> Updating application code to deal
On Sat, May 31, 2008 at 6:31 PM, r.m.oudkerk <[EMAIL PROTECTED]> wrote:
> On 31/05/2008, Paul Moore <[EMAIL PROTECTED]> wrote:
>> 2008/5/30 Farshid Lashkari <[EMAIL PROTECTED]>:
>>> I'm not sure if there will be any side affects to modifying
>>> sys.executable though. Should this be the official wa
[EMAIL PROTECTED] wrote:
Nick> We fixed the module names that used mixed case - the amount of
Nick> work that turned out to be involved in just doing that much for
Nick> PEP 3108 makes me shudder at the thought of trying to fix all of
Nick> the standard library APIs that currently
Guido van Rossum wrote:
This PEP is incomplete without specifying exactly which built-in and
stdlib types should be registered as String instances.
I'm also confused -- the motivation seems mostly "so that you can skip
iterating over it when flattening a nested sequence" but earlier you
rejected
From: "Guido van Rossum" <[EMAIL PROTECTED]>
All this makes me lean towards a rejection of this proposal -- it
seems worse than no proposal at all. It could perhaps be rescued by
adding some small set of defined operations.
By subclassing Sequence, we get index() and count() mixins for free.
W
Please try to find the largest set of methods that you're comfortable
with. __add__ comes to mind.
Note that if you add __hash__, this rules out bytearray -- is that
your intention? __hash__ is intentionally not part of the "read-only"
ABCs because read-only doesn't mean immutable.
Also, (again)
On 2008-06-02 01:30, Gregory P. Smith wrote:
On Fri, May 30, 2008 at 1:37 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
Sorry, I probably wasn't clear enough:
Why can't we have both PyString *and* PyBytes exposed as C
APIs (ie. visible in code and in the linker) in 2.x, with one redirecting
to t
On 5/31/08, Mark Hammond <[EMAIL PROTECTED]> wrote:
> So it seems that maybe simply "setExecutable()" isn't the correct
> abstraction here, but maybe a "factory" approach, so the entire process
> creation mechanism can be replaced rather than just the name of the
> executable to spawn?
Indeed.
Nick> We fixed the module names that used mixed case - the amount of
Nick> work that turned out to be involved in just doing that much for
Nick> PEP 3108 makes me shudder at the thought of trying to fix all of
Nick> the standard library APIs that currently don't follow the style
Are you completelly sure of adding those guys: PyBytes_InternXXX ???
On 6/1/08, Gregory P. Smith <[EMAIL PROTECTED]> wrote:
> On Fri, May 30, 2008 at 1:37 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> > On 2008-05-30 00:57, Nick Coghlan wrote:
> >>
> >> M.-A. Lemburg wrote:
> >>>
> >>> * W
On Mon, Jun 2, 2008 at 5:33 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
>
>> Okay, how about this? http://codereview.appspot.com/1521
>>
>> Using that patch, both PyString_ and PyBytes_ APIs are available using
>> function stubs similar to the above. I opted to define the stub
>> functions righ
-cc: python-3000
I believe those APIs are already there in the existing interface. Why does
that concern you?
On Mon, Jun 2, 2008 at 9:17 AM, Lisandro Dalcin <[EMAIL PROTECTED]> wrote:
> Are you completelly sure of adding those guys: PyBytes_InternXXX ???
>
>
> On 6/1/08, Gregory P. Smith <[EM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We are going to postpone the first beta releases by one week. We had
some problems with mail.python.org today, which prompted a query to
Guido from me about the postponement. mail.python.org should now be
back up normally now, as evidenced by
I will freely admit that I haven't followed this thread in any detail,
but if it were up to me, I'd have the 2.6 internal code use PyString
(as both what the linker sees and what the human reads in the source
code) and the 3.0 code use PyBytes for the same thing. Let the merges
be damed -- most cha
On Mon, Jun 2, 2008 at 4:09 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I will freely admit that I haven't followed this thread in any detail,
> but if it were up to me, I'd have the 2.6 internal code use PyString
...
Should we read this as a BDFL pronouncement and make it so?
All that wo
On Sat, May 24, 2008 at 3:15 PM, Paul Moore <[EMAIL PROTECTED]> wrote:
>
> > As for PDCurses library itself there is a Makefile in PDCurses
> distribution
> > for Microsoft Visual C++ 2.0+ named vcwin32.mak I can't afford buying
> > Visual Studio to test if it works with newer versions, but logic
On Mon, Jun 2, 2008 at 3:51 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> We are going to postpone the first beta releases by one week. We had some
> problems with mail.python.org today, which prompted a query to Guido from me
> about the postpon
On Mon, Jun 2, 2008 at 7:22 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>>
>
> Now is as good a time as any to mention that on Wednesday I am flying
> out to help my mother move. I don't know when she is going to have her
> Internet connection set up, so I might not be back online until June
> 16.
Hi all,
As a newly converted fan of str.format, it gives me pangs to see the
whole stdlib using "%." I realize that str.format is not quite up to
the speed standards we'd like, but I'm sure that will change.
In any case, I'm willing to give the TLC to convert the whole stdlib
to str.format, so I j
On Mon, Jun 2, 2008 at 5:49 PM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
> As a newly converted fan of str.format, it gives me pangs to see the
> whole stdlib using "%." I realize that str.format is not quite up to
> the speed standards we'd like, but I'm sure that will change.
>
> In any case,
21 matches
Mail list logo
