On 1/2/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 2, 2007, at 7:52 PM, Brett Cannon wrote:
>> base64 and quopri implement specific RFCs so I think they should
>> stay. uu implements a defacto standard, but I don't like its
>> interface (it
On 1/2/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 2, 2007, at 10:53 PM, Anthony Baxter wrote:
> Additionally, base32 and base16 are not supported by codecs,
> according to the docs, and neither is the ability to specify
> alternate characte
On 1/2/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 2, 2007, at 7:51 PM, Bill Janssen wrote:
> Let me suggest a consolidation idea I don't see there: a grouping
> similar to that which has been done with email, but called "web".
> This packa
On 1/3/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Jan 2, 2007, at 6:47 PM, Brett Cannon wrote:
>
> > Are you at least okay with base64, quopri, and uu going? You are just
> > arguing for the saving of binascii, right?
> >
> > Does anyone el
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 3, 2007, at 2:57 AM, Brett Cannon wrote:
> That's an idea if someone is up for doing that. Could also hide
> binascii as
> _binascii and have base64, quopri, and uu use it then to follow
> what we are
> doing with cStringIO/StringIO et. al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 3, 2007, at 3:02 AM, Brett Cannon wrote:
> I bet using an absolute import on the part of the codecs module to
> specify
> the encodings package would deal with a lot of your worries.
Indeed!
- -Barry
-BEGIN PGP SIGNATURE-
Version: G
On 1/2/07, Anthony Baxter <[EMAIL PROTECTED]> wrote:
> base64.encodestring('hello world')
> or
> base64.b64encode('hello world')
>
> become
> codecs.getencoder('base64')('hello')[0]
Isn't this a lot more idiomatically translated as
'hello world'.encode('base64')
or is there still too much worr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 3, 2007, at 9:23 AM, Michael Urman wrote:
> On 1/2/07, Anthony Baxter <[EMAIL PROTECTED]> wrote:
>> base64.encodestring('hello world')
>> or
>> base64.b64encode('hello world')
>>
>> become
>> codecs.getencoder('base64')('hello')[0]
>
> Isn't th
On 1/2/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 05:48 PM 1/2/2007 -0600, Collin Winter wrote:
> >Is whatever savings you see there worth changing the language for? Is
> >function overloading really that important and that common?
>
> Ah, but now you're making a different argument. Your o
> Isn't this a lot more idiomatically translated as
> 'hello world'.encode('base64')
> or is there still too much worry that this will require
> encoding/decoding ascii bytestrings?
Will this work properly in Python 3K? I tend to use base64, for
example, to turn byte sequences into safe strin
On 1/2/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > On 1/1/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > > will introduce a cycle from err -> traceback -> stack frame -> err,
> The problem with a weakref is that it won't keep the tb alive when you
> save the exception for later (as is
On 1/3/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> PS: I think it's interesting how nearly all the use-cases mentioned
> involve adding type information to functions.
Not surprising, since that's the context where this was first brought
up. The earliest proposals *did* suggest standard type-che
At 11:06 AM 1/3/2007 -0600, Collin Winter wrote:
>I don't see annotations and decorators as falling in to the same
>category in that respect. Decorators make life easier for a much wider
>audience than do annotations. Everyone uses decorators, but how many
>people write/use Java/ObjC bridges?
Um,
Have the deprecations proposed by PEP 324
(http://www.python.org/dev/peps/pep-0324/), the subprocess module,
been forgotten or am I blind?
"The functions and modules that this new module is trying to
replace (os.system, os.spawn*, os.popen*, popen2.*, commands.*)
are expected to be available in fu
"Brett Cannon" <[EMAIL PROTECTED]> wrote:
> I don't remember the whole bytes discussion in terms of encoding and
> decoding.
Check "the bytes type" summary and threads here:
http://mail.python.org/pipermail/python-dev/2006-April/063588.html
Also check the "encode and decode interface in Python 3
Barry Warsaw <[EMAIL PROTECTED]> wrote:
> On Jan 3, 2007, at 9:23 AM, Michael Urman wrote:
> > On 1/2/07, Anthony Baxter <[EMAIL PROTECTED]> wrote:
> >> base64.encodestring('hello world')
> >> or
> >> base64.b64encode('hello world')
> >>
> >> become
> >> codecs.getencoder('base64')('hello')[0]
> >
On 1/3/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 11:06 AM 1/3/2007 -0600, Collin Winter wrote:
> >PS: I think it's interesting how nearly all the use-cases mentioned
> >involve adding type information to functions.
>
> Um, yeah, that was kind of the idea. :)
I mention that as an amusing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 3, 2007, at 1:44 PM, Josiah Carlson wrote:
> What about:
>
> 'hello world'.encode.base64()
>
> Then incorrectly named encodings can raise an attribute error. Users
> can discover what they can encode/decode their objects to via dir
> (obj
On 1/3/07, BJörn Lindqvist <[EMAIL PROTECTED]> wrote:
Have the deprecations proposed by PEP 324
(http://www.python.org/dev/peps/pep-0324/), the subprocess module,
been forgotten or am I blind?
I forgot.
"The functions and modules that this new module is trying to
replace (os.system, os.spaw
At 01:00 PM 1/3/2007 -0600, Collin Winter wrote:
>On 1/3/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
>>At 11:06 AM 1/3/2007 -0600, Collin Winter wrote:
>> >PS: I think it's interesting how nearly all the use-cases mentioned
>> >involve adding type information to functions.
>>
>>Um, yeah, that was
> Also, now that you remind me of it, IronPython could use [annotations] for C#
> overloads.
FWIW, the IronPython folks are looking for a CPython-compatible syntax
for specifying .net attributes. Function decorators (plus class
decorators) don't cover all the use cases because so many different
On 2 Jan, 2007, at 1:14, Brett Cannon wrote:
* buildtools
2.3
This one is still used by buildapplet (a mac specific tool/module).
However, see below for more on this.
* cfmfile
2.4
mac specific, I don't know if this works on OSX (Jack probably knows).
* macfs
2.3
Mac spe
Barry Warsaw <[EMAIL PROTECTED]> wrote:
> On Jan 3, 2007, at 1:44 PM, Josiah Carlson wrote:
>
> > What about:
> >
> > 'hello world'.encode.base64()
> >
> > Then incorrectly named encodings can raise an attribute error. Users
> > can discover what they can encode/decode their objects to via d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 3, 2007, at 3:48 PM, Josiah Carlson wrote:
>> That's better. I'm not sure it's a total win over what we have now,
>> unless you're thinking that the mapping between .encode.
>> and .encode('whatever') is automatic.
>
> I'm thinking that .encod
On 1/3/07, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
On 2 Jan, 2007, at 1:14, Brett Cannon wrote:
>
> * buildtools
>2.3
This one is still used by buildapplet (a mac specific tool/module).
However, see below for more on this.
Since the deprecation has already occurred it's out of my h
On 3 Jan, 2007, at 22:07, Brett Cannon wrote:
On 1/3/07, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
On 2 Jan, 2007, at 1:14, Brett Cannon wrote:
>
> * buildtools
>2.3
This one is still used by buildapplet (a mac specific tool/module).
However, see below for more on this.
Since the de
On 1/3/07, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
On 3 Jan, 2007, at 22:07, Brett Cannon wrote:
On 1/3/07, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
>
>
> On 2 Jan, 2007, at 1:14, Brett Cannon wrote:
>
>
> >
> > * buildtools
> >2.3
>
> This one is still used by buildapplet (a mac sp
On 1/2/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> For example, interfacing to at least Java and Objective C have also been
> mentioned as use cases, and I can think of a variety of other uses such as
> database query mapping, predicate logic functions, and web or other types
> of RPC parameter
On Jan 3, 2007, at 1:59 PM, Collin Winter wrote:
> On 1/2/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
>> For example, interfacing to at least Java and Objective C have
>> also been
>> mentioned as use cases, and I can think of a variety of other uses
>> such as
>> database query mapping, pr
On Wed, 3 Jan 2007, Adam Olsen wrote:
> That can be solved by moving the weakref to the stack frame -> exc
> part, and only turning it from a strong reference into a weak
> reference when the function exits. When debugging via the raised
> exception, the chain of __context__ references would keep
On 1/3/07, Ka-Ping Yee <[EMAIL PROTECTED]> wrote:
> On Wed, 3 Jan 2007, Adam Olsen wrote:
> > That can be solved by moving the weakref to the stack frame -> exc
> > part, and only turning it from a strong reference into a weak
> > reference when the function exits. When debugging via the raised
>
At 07:38 PM 1/3/2007 -0800, Guido van Rossum wrote:
>On 1/3/07, Ka-Ping Yee <[EMAIL PROTECTED]> wrote:
> > On Wed, 3 Jan 2007, Adam Olsen wrote:
> > > That can be solved by moving the weakref to the stack frame -> exc
> > > part, and only turning it from a strong reference into a weak
> > > referen
On 1/3/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> Or perhaps translate blocks of the form:
>
> except ExcType, e:
> # body
>
> to:
>
> except ExcType, e:
> try:
> # body
> finally:
> del e
>
> This won't stop you from creating a cy
On 1/3/07, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
>
> On 2 Jan, 2007, at 1:14, Brett Cannon wrote:
>
> > * Mac
> >+ applesingle
> >- Undocumented.
> >* AppleSingle is a binary file format for A/UX.
> >+ A/UX no longer distributed.
>
> No problems here.
I
At 09:11 PM 1/3/2007 -0800, Guido van Rossum wrote:
>On 1/3/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
>>Or perhaps translate blocks of the form:
>>
>> except ExcType, e:
>> # body
>>
>>to:
>>
>> except ExcType, e:
>> try:
>> # body
>> finally:
>
On 4 Jan, 2007, at 6:30, Neal Norwitz wrote:
On 1/3/07, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
On 2 Jan, 2007, at 1:14, Brett Cannon wrote:
> * Mac
>+ applesingle
>- Undocumented.
>* AppleSingle is a binary file format for A/UX.
>+ A/UX no longer d
On 1/3/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
>Or perhaps translate blocks of the form:
>
> except ExcType, e:
> # body
>
>to:
>
> except ExcType, e:
> try:
> # body
> finally:
> del e
That's much nicer! (I feel silly now for n
37 matches
Mail list logo
