On Dec 23, 2004, at 23:12, Martin v. Löwis wrote:
Barry Scott wrote:
It seems that I can build extensions with msvc 6.0 that work with the
python 2.4 windows
binary kit.
Is this safe?
No, it isn't. This emerges as a Python 2.4 FAQ.
I recall warning a while ago about mixing msvc 6.0 and msvc 7.1
r
Barry Scott wrote:
It seems that I can build extensions with msvc 6.0 that work with the
python 2.4 windows
binary kit.
Is this safe?
No, it isn't. This emerges as a Python 2.4 FAQ.
I recall warning a while ago about mixing msvc 6.0 and msvc 7.1 runtime
DLL's. Is this
an issue with python 2.4?
Y
I see that, as expected, windows python 2.4 was built with MSVC 7.1
rather then msvc 6.0.
It seems that I can build extensions with msvc 6.0 that work with the
python 2.4 windows
binary kit.
Is this safe?
I recall warning a while ago about mixing msvc 6.0 and msvc 7.1 runtime
DLL's. Is this
an
Dear Python User:
Following my last message, I am pleased to be able to
announce that you can register for PyCon DC 2005 on the
web at
http://www.python.org/pycon/2005/register.html
starting at 1700 EST today (December 23). Thanks to
George Belotsky of Open Light Software for assistance
in
> It turns out the major mistake I made was to start from "docs.python.org"
> instead of "www.python.org/doc".
If you ask me that wasn't your mistake but the mistake of whoever
decided to create a subdomain for docs (or for anything else).
--
--Guido van Rossum (home page: http://www.python.org
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,
-> >
I just spent 10 minutes hunting through the Python website for this link:
http://www.python.org/doc/newstyle.html
I knew it was there somewhere, I just couldn't find the darn thing.
It turns out the major mistake I made was to start from "docs.python.org"
instead of "www.python.org/doc".
Would it
11 matches
Mail list logo
