On 11/12/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
>
> > IMO it was an oversight. Or we were all exhausted. I keep copying
> > those three classes from the docs, which is silly. :-)
>
> I'll whip up a patch. would the "embedded python module" approach I'm
> using for _
[EMAIL PROTECTED] wrote:
> >> Right. There seem to be people who believe that 1e6 is an int.
> ...
> Steve> Next thing you know some damned fool is going to suggest that 1e6
> Steve> gets parsed into a long integer.
>
> Maybe in Py3k a decimal point should be required in floats usi
>> Right. There seem to be people who believe that 1e6 is an int.
...
Steve> Next thing you know some damned fool is going to suggest that 1e6
Steve> gets parsed into a long integer.
Maybe in Py3k a decimal point should be required in floats using exponential
notation - 1.e6 or 1.
On 11/13/06, Steve Holden <[EMAIL PROTECTED]> wrote:
> In which case an immediate transition to error status would seem to
> offer a way of providing an effective education. Deprecation may well be
> the best way to go for customer-friendliness, but anyone who believes
> 1e6 is an int should be hit
Guido van Rossum wrote:
> On 11/12/06, Anthony Baxter <[EMAIL PROTECTED]> wrote:
>> On Sunday 12 November 2006 22:09, Fredrik Lundh wrote:
>>> Martin v. Löwis wrote:
Patch #1067760 deals with passing of float values to file.seek;
the original version tries to fix the current implementatio
