On Fri, Aug 12, 2005, David Goodger wrote:
>
> Barry Warsaw and I, the PEP editors, have been discussing the
> need for a new PEP type lately. Martin von L?wis' PEP 347 was
> a prime example of a PEP that didn't fit into the existing
> Standards Track and Informational categories. We agreed upon
Hi all,
recently I've tried to use dl module functionality to interface with
external C function.
(It was a quick hack so I didn't want to write wrapper code). To my
dismay I learned that
call method doesn't allow passing data by reference (since strings are
immutable in
python) - but passing poin
In the C version of expat, handlers receive a void *userdata, but it is
not the case in the python version.
This means one cant parse multiple files at the same time using the same
handlers. You cant pass the context current context to the handler, you must
base your code on global variables which
Barry Warsaw and I, the PEP editors, have been discussing the need for a new PEP
type lately. Martin von Löwis' PEP 347 was a prime example of a PEP that didn't
fit into the existing Standards Track and Informational categories. We agreed
upon a new "Process" PEP type. For more information, plea
martin> Log Message:
martin> Add wush.net hosting.
...
martin> + * Greg Stein suggested http://www.wush.net/subversion.php.
...
I will enthusiastically cast my vote for tummy.com, Sean Reifschneider's
company. Mojam leases a server there (Mojam & Musi-Cal websites running
C
Anthony Baxter wrote:
> So I'm currently planning for a 2.4.2 sometime around mid September. I figure
> we cut a release candidate either on the 7th or 14th, and a final a week
> later.
I'm returning only on Sep 12 from vacation, so the Windows binaries of a
release candidate would have to wait
[Josiah]
> At this point, I'd be happy to get
> /any/ mechanism, with a preference to struct and/or binascii
Assign 1023290 to me and I'll get it done in the next month or so.
Raymond
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pytho
On 8/12/05, Thomas Heller <[EMAIL PROTECTED]> wrote:
> Brett Cannon <[EMAIL PROTECTED]> writes:
>
> > On 8/10/05, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> >> > > Then I don't follow what you mean by "moved under os".
> >> >
> >> > In other words, to get the exception, do ``from os import
> >
For 2.5a1...
Some exposure of _PyLong_AsByteArray() and _PyLong_FromByteArray() to
Python. There was a discussion about this almost a year ago
(http://python.org/sf/1023290), and no mechanism (struct format code
addition, binascii.tolong/fromlong, long.tostring/fromstring, ...)
actually made it in
> At the moment I'm trying to create a minimal file that when imported fails
> with 2.4.1 . I'll update the case as soon as I have one, but I wanted to
> draw some attention in python-dev in case it rings a bell.
Please ignore my previous message --through gmane I saw only mwh's message,
and aft
"Michael Hudson" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Anthony Baxter <[EMAIL PROTECTED]> writes:
>
>> So I'm currently planning for a 2.4.2 sometime around mid September. I
>> figure
>> we cut a release candidate either on the 7th or 14th, and a final a week
>> later.
>
>
[Paolino]
> I can't contact sourceforge bug tracker sorry.
I've added a bug report for you:
www.python.org/sf/1257731
> set.remove is trying to freeze sets when they are used as keys.No
matter
> if an __hash__ method is defined.
Will fix. Feel free to email me off-list with any questions.
I can't contact sourceforge bug tracker sorry.
set.remove is trying to freeze sets when they are used as keys.No matter
if an __hash__ method is defined.
This is incoherent with Set.remove and dict.__delete__ & co.
If this is a feature ,then I ask strongly to keep sets module in the
stdlib f
On Thu, 2005-08-11 at 20:51, Anthony Baxter wrote:
> So I'm currently planning for a 2.4.2 sometime around mid September. I figure
> we cut a release candidate either on the 7th or 14th, and a final a week
> later.
Cool. I'd like to commit the patches in this bug report:
https://sourceforge.n
Michael Hudson wrote:
> Anthony Baxter <[EMAIL PROTECTED]> writes:
>
>>So I'm currently planning for a 2.4.2 sometime around mid September. I figure
>>we cut a release candidate either on the 7th or 14th, and a final a week
>>later.
>
> Cool. I'm not sure how many outstanding bugs should be
Anthony Baxter <[EMAIL PROTECTED]> writes:
> So I'm currently planning for a 2.4.2 sometime around mid September. I figure
> we cut a release candidate either on the 7th or 14th, and a final a week
> later.
Cool. I'm not sure how many outstanding bugs should be fixed before
2.4.2. Some stuff
Hello,
Would it perhaps be an idea, given the number of users posting to the
dev list, to put a rather obvious warning on the listinfo page:
http://mail.python.org/mailman/listinfo/python-dev
Something like
Do not post general Python questions to this list! For help
with Python
"Michael Hudson" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> Guard? Monitor? Don't really like either of these.
>
I know I am late, but since guard means something else, 'sentinel' (in the
line of __enter__ and __exit__ interpretation) could be an alternative.
Tongue in ch
Brett Cannon <[EMAIL PROTECTED]> writes:
> On 8/10/05, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
>> > > Then I don't follow what you mean by "moved under os".
>> >
>> > In other words, to get the exception, do ``from os import
>> > WindowsError``. Unfortunately we don't have a generic win modu
19 matches
Mail list logo
