On 19 October 2010 05:52, Éric Araujo mer...@netwok.org wrote:
Congratulations Victor! This is not a small feat. The PSU should send
you cookies to thank you, but they won’t since they don’t exist and
What? Cookies don't exist???
Paul.
___
On Mon, 18 Oct 2010 22:27:06 -0500
Ron Adam r...@ronadam.com wrote:
Could something like (or parts of) the following work? It would have
assignment and module keywords items as well.
Well, this is very nice, except that the more complicated the form is,
the less likely people are to fill it
Victor Stinner wrote:
Hi,
Seven months after my first commit related to this issue, the full test suite
of Python 3.2 pass with ASCII, ISO-8859-1 and UTF-8 locale encodings in a non-
ascii source directory. It means that Python 3.2 now process correctly
filenames in all modules, build
On Tue, Oct 19, 2010 at 11:53 AM, Victor Stinner
victor.stin...@haypocalc.com wrote:
Hi,
Seven months after my first commit related to this issue, the full test suite
of Python 3.2 pass with ASCII, ISO-8859-1 and UTF-8 locale encodings in a non-
ascii source directory. It means that Python
On Oct 19, 2010, at 03:53 AM, Victor Stinner wrote:
Seven months after my first commit related to this issue, the full test suite
of Python 3.2 pass with ASCII, ISO-8859-1 and UTF-8 locale encodings in a non-
ascii source directory. It means that Python 3.2 now process correctly
filenames in
At 08:03 AM 10/18/2010 +1000, Nick Coghlan wrote:
I'm a little dubious about exposing these officially. They're mainly a
hack to get some parts of the standard library working (e.g. runpy) in
the absence of full PEP 302 support in the imp module, not really
something we want to encourage anyone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Current Python lacks support for aio_* syscalls to do async IO. I
think this could be a nice addition for python 3.3.
If you agree, I will create an issue in the tracker. If you think the
idea is of no value, please say so for me to move on. Maybe an
Yes, that would be a nice addition. -peter
On 10/19/10 12:50 PM, Jesus Cea j...@jcea.es wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Current Python lacks support for aio_* syscalls to do async IO. I
think this could be a nice addition for python 3.3.
If you agree, I will create
On 04:50 pm, j...@jcea.es wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Current Python lacks support for aio_* syscalls to do async IO. I
think this could be a nice addition for python 3.3.
Adding more platform wrappers is always nice. Keep in mind that the
quality of most (all?)
You should file a new issue on the bug tracker but unless you have a
patch to propose it's unlikely that someone else is gonna implement
it.
Regards
--- Giampaolo
http://code.google.com/p/pyftpdlib/
http://code.google.com/p/psutil/
2010/10/19 Jesus Cea j...@jcea.es:
-BEGIN PGP SIGNED
Am 19.10.2010 16:12, schrieb Barry Warsaw:
On Oct 19, 2010, at 03:53 AM, Victor Stinner wrote:
Seven months after my first commit related to this issue, the full test suite
of Python 3.2 pass with ASCII, ISO-8859-1 and UTF-8 locale encodings in a non-
ascii source directory. It means that
On Oct 19, 2010, at 1:47 PM, exar...@twistedmatrix.com wrote:
Adding more platform wrappers is always nice. Keep in mind that the quality
of most (all?) aio_* implementations is spotty at best, though. On Linux,
they will sometimes block (for example, if you fail to align buffers
Am 19.10.2010 17:26, schrieb vinay.sajip:
Author: vinay.sajip
Date: Tue Oct 19 17:26:24 2010
New Revision: 85724
Log:
logging: Added _logRecordClass, getLogRecordClass, setLogRecordClass to
increase flexibility of LogRecord creation.
Will this be documented?
Georg
--
Thus spake the
Hello Jesus,
Current Python lacks support for aio_* syscalls to do async IO. I
think this could be a nice addition for python 3.3.
If you agree, I will create an issue in the tracker. If you think the
idea is of no value, please say so for me to move on. Maybe an 3th party
module, but I
Am 19.10.2010 19:47, schrieb exar...@twistedmatrix.com:
On 04:50 pm, j...@jcea.es wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Current Python lacks support for aio_* syscalls to do async IO. I
think this could be a nice addition for python 3.3.
Adding more platform wrappers is
So, in conclusion, I disagree that adding wrappers for these would be
nice. It wouldn't. It would cause some people to think they would be
useful things to call, and they would always be wrong.
We are all consenting adults. If people want to shoot themselves in
their feet, we let them. For
Also, the canonical way to do file I/O in Python 3 is the `io` lib,
therefore it would be a bit of a shame to have separate, non-integrated
`aio_*` functions.
I disagree. We also have posix.open, posix.dup, etc. We always expose
POSIX functions in the posix module (except for the socket
Le mercredi 20 octobre 2010 à 00:48 +0200, Martin v. Löwis a écrit :
Also, the canonical way to do file I/O in Python 3 is the `io` lib,
therefore it would be a bit of a shame to have separate, non-integrated
`aio_*` functions.
I disagree. We also have posix.open, posix.dup, etc. We
On Oct 19, 2010, at 6:44 PM, Martin v. Löwis wrote:
So, in conclusion, I disagree that adding wrappers for these would be
nice. It wouldn't. It would cause some people to think they would be
useful things to call, and they would always be wrong.
We are all consenting adults. If people want
Le mardi 19 octobre 2010 16:12:56, Barry Warsaw a écrit :
Going forward, is there adequate documentation, guidelines, and safeguards
for future coders so that they Do The Right Thing with new code? Perhaps
a short How To in the standard documentation would be helpful, with links
to it from
Where should I send this patch?
diff -u fpconst-0.7.2/fpconst.py fpconst-0.7.2.new/fpconst.py
--- fpconst-0.7.2/fpconst.py2005-02-24 12:42:03.0 -0500
+++ fpconst-0.7.2.new/fpconst.py2010-10-19 20:55:07.407765664 -0400
@@ -40,18 +40,18 @@
ident = $Id: fpconst.py,v 1.16
fpconst developers?
2010/10/19 Neal Becker ndbeck...@gmail.com:
Where should I send this patch?
diff -u fpconst-0.7.2/fpconst.py fpconst-0.7.2.new/fpconst.py
--- fpconst-0.7.2/fpconst.py 2005-02-24 12:42:03.0 -0500
+++ fpconst-0.7.2.new/fpconst.py 2010-10-19
On Oct 19, 2010, at 8:09 PM, James Y Knight wrote:
There's a difference.
os._exit is useful. os.open is useful. aio_* are *not* useful. For anything.
If there's anything you think you want to use them for, you're wrong. It
either won't work properly or it will worse performing than the
On 01:37 am, gl...@twistedmatrix.com wrote:
On Oct 19, 2010, at 8:09 PM, James Y Knight wrote:
There's a difference.
os._exit is useful. os.open is useful. aio_* are *not* useful. For
anything. If there's anything you think you want to use them for,
you're wrong. It either won't work
On Tue, Oct 19, 2010 at 8:37 PM, Glyph Lefkowitz
gl...@twistedmatrix.com wrote:
I'd like to echo this sentiment. This is not about providing a 'safe'
wrapper to hide some powerful feature of these APIs: the POSIX aio_*
functions are really completely useless.
To quote the relevant standard
25 matches
Mail list logo
