Titus Brown <[EMAIL PROTECTED]> wrote:
>
> -> > 1067760 -- float-->long conversion on fileobj.seek calls, rather than
> -> >float-->int. Permits larger floats (2.0**62) to match large
> -> >int (2**62) arguments. rhettinger marked as "won't fix" in
> -> >the original bug
Titus Brown <[EMAIL PROTECTED]> writes:
> -> > Apparently file.seek doesn't have this DeprecationWarning though..
> -> > Strange, that.
> -> > >>> f.seek(3.6)
> -> > >>> f.tell()
> -> > 3L
> ->
> -> That's a bug. Who'll fix it?
>
> Added:
>
> + if (PyFloat_Check(offobj))
> +
Titus Brown <[EMAIL PROTECTED]> writes:
> -> > 1067760 -- float-->long conversion on fileobj.seek calls, rather than
> -> >float-->int. Permits larger floats (2.0**62) to match large
> -> >int (2**62) arguments. rhettinger marked as "won't fix" in
> -> >the original bug r
-> > Apparently file.seek doesn't have this DeprecationWarning though..
-> > Strange, that.
-> > >>> f.seek(3.6)
-> > >>> f.tell()
-> > 3L
->
-> That's a bug. Who'll fix it?
Added:
+ if (PyFloat_Check(offobj))
+ PyErr_Warn(PyExc_DeprecationWarning,
+
-> > 1067760 -- float-->long conversion on fileobj.seek calls, rather than
-> >float-->int. Permits larger floats (2.0**62) to match large
-> >int (2**62) arguments. rhettinger marked as "won't fix" in
-> >the original bug report; this seems like a clean solution,
-> >
> Apparently file.seek doesn't have this DeprecationWarning though..
> Strange, that.
> >>> f.seek(3.6)
> >>> f.tell()
> 3L
That's a bug. Who'll fix it?
--
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Python-Dev mailing list
Pyth
On Dec 23, 2004, at 12:36 AM, Timothy Fitz wrote:
1067760 -- float-->long conversion on fileobj.seek calls, rather than
float-->int. Permits larger floats (2.0**62) to match large
int (2**62) arguments. rhettinger marked as "won't fix" in
the original bug report; this seems l
> 1067760 -- float-->long conversion on fileobj.seek calls, rather than
>float-->int. Permits larger floats (2.0**62) to match large
>int (2**62) arguments. rhettinger marked as "won't fix" in
>the original bug report; this seems like a clean solution,
>tho. Recom
-> Jeremy Hylton wrote:
-> >I got started on these this morning, will likely finish them tomorrow.
-> > It would be perverse to apply your patch last, wouldn't it?
->
-> It turns out that Titus' patch might be more involved than he thought
-> it would be.
*shrug* that's life ;). I stole my patch
Martin v. Löwis wrote:
Jeremy Hylton wrote:
I got started on these this morning, will likely finish them tomorrow.
It would be perverse to apply your patch last, wouldn't it?
It turns out that Titus' patch might be more involved than he thought
it would be.
In any case, the review itself is a hig
Jeremy Hylton wrote:
I got started on these this morning, will likely finish them tomorrow.
It would be perverse to apply your patch last, wouldn't it?
It turns out that Titus' patch might be more involved than he thought
it would be.
In any case, the review itself is a highly appreciated contribu
On Sun, 19 Dec 2004 02:13:24 -0800, Titus Brown <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> per previous discussion,
>
> http://mail.python.org/pipermail/python-dev/2004-October/049495.html
>
> I'd like to push a trivial little patch to sgmllib (#1087808) on you
> gents, in exchange for
12 matches
Mail list logo
