Hi py3k,
First of all, excuse me for taking your time. I am new to the list
so, not familiar with the processes specific to the list, if any.
I am new to the list (joined a week back) but not new to Python having
coded in it for a fair bit of time and contributed open source code in Pyt
Martin v. Löwis wrote:
> It's currently called lib2to3,
> so I can't see why two2three would be better
I was just thinking that '2to3' wouldn't be a valid
module name. I guess 'lib2to3' works too (or 2),
and is easier 2 type 2.
--
Greg
___
Python-3000
Dnia 16-03-2008, N o godzinie 18:20 -0400, Terry Reedy pisze:
> The rule I suggested is 'execute the statement the same *as if* the
> iterable items had been written in the code as a comma sequence'.
One reason I don't like this rule is that it works on the level of the
token sequence rather th
On Mon, Mar 17, 2008 at 2:48 AM, Anand Balachandran Pillai <
[EMAIL PROTECTED]> wrote:
> Hi py3k,
>
> First of all, excuse me for taking your time. I am new to the list
> so, not familiar with the processes specific to the list, if any.
>
>
> I am new to the list (joined a week back) bu
Glad you want to help!
You can find plenty of things to do in the bug tracker at
bugs.python.org. Note that 2.6 needs as much (or more!) love as 3.0 at
this point. (2.6 is being developed in the svn trunk.) Feel free to
tentatively pick a project and send mail here asking if that's
something we'd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 16, 2008, at 6:46 PM, Barry Warsaw wrote:
>
> 'critical' is fine (or 'immediate'). My problem before was that I
> couldn't do one query that gave me all the critical issues for both
> 2.6 and 3.0. That certainly could have been pebkac though.
I accidentally sent this reply to Benjamin, sorry for the two copies:
I'm brand new on this list as well, so take what I say with a grain of
salt, but a group of us here at PyCon are about to start sprinting,
and they've given us some very good resources to help us get started.
Brett Canno
Hi,
What's the current status of I/O in Py3k?
Are plans there to implement some if not all of io.py in C. (If not, I can
work on this.)
Also, is I/O going to be backported to 2.6?
Thanks,
Benjamin Peterson
___
Python-3000 mailing list
Python-3000@python.
On Mon, Mar 17, 2008 at 12:21 PM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
> What's the current status of I/O in Py3k?
Ping is looking at it. There are quite a few things broken in the
handling of seek/tell on text files.
> Are plans there to implement some if not all of io.py in C. (If not,
Guido's asked me to give a quick status report, so here I go..
The critical parts of the design and implementation are basically
done. I've implemented monitors to contain objects without an
explicit thread-safe API, which then let me remove the GIL. I've
created a synchronous/asynchronous refco
Thanks! Would you care to give us a hint on how a typical
multi-threaded application would be written using this approach? How
much pre-existing code would break do you expect?
On Mon, Mar 17, 2008 at 12:56 PM, Adam Olsen <[EMAIL PROTECTED]> wrote:
> Guido's asked me to give a quick status report,
On Mon, Mar 17, 2008 at 1:02 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Mon, Mar 17, 2008 at 12:56 PM, Adam Olsen <[EMAIL PROTECTED]> wrote:
> > Guido's asked me to give a quick status report, so here I go..
> >
> > The critical parts of the design and implementation are basically
>
"Marcin 'Qrczak' Kowalczyk" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
| Dnia 16-03-2008, N o godzinie 18:20 -0400, Terry Reedy pisze:
|
| > The rule I suggested is 'execute the statement the same *as if* the
| > iterable items had been written in the code as a comma sequence'.
For those who don't read blogs, I just blogged the slides for my
keynote, and added an important admonishment to 3rd party developers.
Here's the full text of the blog:
The slides of my `keynote`_ are now up on python.org. There's both a
`PowerPoint`_ and a `PDF`_ file.
.. _keynote: http://www.p
Greetings from Pycon 2008!
Neal Norwitz and I have worked out the schedule for Python 2.6 and
3.0, which will be released in lockstep. We will be following a
monthly release schedule, with releases to occur on the first
Wednesday of the month. We'll move to a 2 week schedule for the
rel
Now I apparently need an email reader that understands reStructuredText :-).
Bill
___
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/arc
I'm the maintainer of a few Python packages which wrap native C or C+
+ code.
At Pycon, I learned that PyPy and Jython support ctypes or have plans
to do so in the near future. I don't know about IronPython.
However, having CPython, PyPy, and Jython all supporting ctypes makes
it the obviou
17 matches
Mail list logo
