On Thu, Oct 18, 2012 at 5:41 PM, Georg Brandl g.bra...@gmx.net wrote:
On 10/18/2012 03:16 PM, Daniel Holth wrote:
On Thu, Oct 11, 2012 at 1:36 PM, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
Daniel Holth dholth at gmail.com writes:
How does this compare to the markerlib approach? In markerlib
On Fri, Oct 19, 2012 at 3:13 PM, Nick Coghlan ncogh...@gmail.com wrote:
Given the way complex numbers interact with floats generally,
returning a complex number with no imaginary component as a floating
point value seems legitimate and the checks in cmath overly strict.
Otherwise you would get
The troublesome Description: parses fine -- as long as there is
anything but a \r\n - for example \r\n - on successive blank lines.
This tends to happen already.
Another solution comes to mind. Put the description in the payload.
The description can have any form, and the installer can stop
On 10/20/2012 10:24 AM, Andrea Griffini wrote:
On Thu, Oct 18, 2012 at 5:41 PM, Georg Brandl g.bra...@gmx.net wrote:
On 10/18/2012 03:16 PM, Daniel Holth wrote:
On Thu, Oct 11, 2012 at 1:36 PM, Vinay Sajip vinay_sa...@yahoo.co.uk
wrote:
Daniel Holth dholth at gmail.com writes:
How does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/19/2012 07:35 PM, Greg Ewing wrote:
Antonio Cuni wrote:
Traceback (most recent call last): File stdin, line 1, in
module TypeError: __complex__ should return a complex object
i.e., the complex constructor does not check that __complex__
Hi,
I'm the author of sh.py, a subprocess module rewrite for Linux and OSX. It
serves as a powerful and intuitive interface to launching subprocesses
http://amoffat.github.com/sh/. It has been maintained on github
https://github.com/amoffat/sh for about 10 months and currently has about
25k
2012/10/20 Andrew Moffat andrew.robert.mof...@gmail.com:
Hi,
I'm the author of sh.py, a subprocess module rewrite for Linux and OSX. It
serves as a powerful and intuitive interface to launching subprocesses
http://amoffat.github.com/sh/. It has been maintained on github
On Sat, Oct 20, 2012 at 12:28 PM, Tres Seaver tsea...@palladion.com wrote:
Exactly: float is perfectly Liskov-substituable for complex; only
applications which do explicit type sniffing can tell the difference,
which makes the sniffing bogus.
You don't have to do explicit sniffing. You could
On 20/10/12 01:13, Nick Coghlan wrote:
On Fri, Oct 19, 2012 at 11:08 PM, Antonio Cunianto.c...@gmail.com wrote:
Is that the real intended behavior?
Given the way complex numbers interact with floats generally,
returning a complex number with no imaginary component as a floating
point value
On Sat, 20 Oct 2012 00:13:51 +1000
Nick Coghlan ncogh...@gmail.com wrote:
On Fri, Oct 19, 2012 at 11:08 PM, Antonio Cuni anto.c...@gmail.com wrote:
Is that the real intended behavior?
Given the way complex numbers interact with floats generally,
returning a complex number with no imaginary
On 21/10/12 06:28, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/19/2012 07:35 PM, Greg Ewing wrote:
Antonio Cuni wrote:
Traceback (most recent call last): File stdin, line 1, in
module TypeError: __complex__ should return a complex object
i.e., the complex
You can check the .image attribute, which exists on floats too (and ints).
--Guido van Rossum (sent from Android phone)
On Oct 20, 2012 6:54 PM, Steven D'Aprano st...@pearwood.info wrote:
On 21/10/12 06:28, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/19/2012
On Sun, Oct 21, 2012 at 12:53 PM, Steven D'Aprano st...@pearwood.info wrote:
Python 2.x legitimately distinguished between floats and complex, e.g.:
py (-100.0)**0.5
Traceback (most recent call last):
File stdin, line 1, in module
ValueError: negative number cannot be raised to a
On Sun, Oct 21, 2012 at 1:38 PM, Chris Angelico ros...@gmail.com wrote:
Python 2 (future directives aside) also required you to explicitly ask
for floating point. That was also changed in Python 3.
Er, should have said that I was referring to division here...
incomplete information. Anyway. Py3
I'm really happy with moving the troublesome Description: field to the
payload. Email Policy() is useful too.
http://hg.python.org/peps/rev/74868fe8ba17
Metadata 1.3 is a ...
+format with no maximum line length, followed by a blank line and an
+arbitrary payload. It is parseable by the
On Sun, Oct 21, 2012 at 11:53 AM, Steven D'Aprano st...@pearwood.info wrote:
On 21/10/12 06:28, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/19/2012 07:35 PM, Greg Ewing wrote:
Antonio Cuni wrote:
Traceback (most recent call last): File stdin, line 1, in
module
On Sat, Oct 20, 2012 at 10:57 PM, Nick Coghlan ncogh...@gmail.com wrote:
PEP 3141 is indeed the driver for these changes, and it's based on the
Python 3.x numeric tower consisting of strict supersets: Complex
Real Rational Integral
Pedant mode: That numeric tower is wrong as it applies to
I think I've changed my mind on this, since it was pointed
out that if you're going to return a float instead of a
complex, you should really be implementing __float__, not
__complex__.
So I think it's fine to require __complex__ to return a
complex, and the docs should perhaps be clarified on
18 matches
Mail list logo
