Le 06/04/2011 03:39, exar...@twistedmatrix.com a écrit :
On 5 Apr, 07:58 pm, mar...@v.loewis.de wrote:
Does this mean new versions of distutils let you build_ext with any
C
compiler, instead of enforcing the same compiler as it has done
previously?
No, it doesn't. distutils was considered
Am 06.04.2011 03:39, schrieb exar...@twistedmatrix.com:
On 5 Apr, 07:58 pm, mar...@v.loewis.de wrote:
Does this mean new versions of distutils let you build_ext with any C
compiler, instead of enforcing the same compiler as it has done
previously?
No, it doesn't. distutils was considered
Am 05.04.2011 00:21, schrieb Antoine Pitrou:
On Mon, 04 Apr 2011 23:40:33 +0200
Martin v. Löwis mar...@v.loewis.de wrote:
- users have expressed concerns that they constantly need to upgrade
VS releases when developing for Python.
Isn't that kind of a misguided argument? It's not Python
Won't that still be an issue despite the stable ABI? Extensions on
Windows should be linked to the same version of MSVCRT used to compile
Python
Not if they use the stable ABI. There still might be issues if you
mix CRTs, but none related to the Python ABI - in particular, none
of those
On 09:55 am, mar...@v.loewis.de wrote:
Am 05.04.2011 00:21, schrieb Antoine Pitrou:
On Mon, 04 Apr 2011 23:40:33 +0200
Martin v. L�wis mar...@v.loewis.de wrote:
- users have expressed concerns that they constantly need to upgrade
VS releases when developing for Python.
Isn't that kind of a
On 09:58 am, mar...@v.loewis.de wrote:
Won't that still be an issue despite the stable ABI? Extensions on
Windows should be linked to the same version of MSVCRT used to compile
Python
Not if they use the stable ABI. There still might be issues if you
mix CRTs, but none related to the Python
On Tue, Apr 5, 2011 at 07:48, exar...@twistedmatrix.com wrote:
On 09:55 am, mar...@v.loewis.de wrote:
Am 05.04.2011 00:21, schrieb Antoine Pitrou:
On Mon, 04 Apr 2011 23:40:33 +0200
Martin v. Löwis mar...@v.loewis.de wrote:
- users have expressed concerns that they constantly need to
On Apr 5, 2011, at 8:52 AM, exar...@twistedmatrix.com wrote:
On 09:58 am, mar...@v.loewis.de wrote:
Won't that still be an issue despite the stable ABI? Extensions on
Windows should be linked to the same version of MSVCRT used to compile
Python
Not if they use the stable ABI. There still
http://www.python.org/dev/peps/pep-0384/ says functions expecting
FILE* are not part of the ABI, to avoid depending on a specific
version of the Microsoft C runtime DLL on Windows. Can extension
modules that need to read and write files practically avoid all of
those functions?
Certainly!
Does this mean new versions of distutils let you build_ext with any C
compiler, instead of enforcing the same compiler as it has done
previously?
No, it doesn't. distutils was considered frozen, and changes to it to
better support the ABI where rejected.
Regards,
Martin
Martin v. Löwis wrote:
Not if they use the stable ABI. There still might be issues if you
mix CRTs, but none related to the Python ABI - in particular, none
of those crashing conditions can arise from the stable ABI.
Won't there still be a problem of your extension module
being linked with a
Am 05.04.2011 22:43, schrieb Greg Ewing:
Martin v. Löwis wrote:
Not if they use the stable ABI. There still might be issues if you
mix CRTs, but none related to the Python ABI - in particular, none
of those crashing conditions can arise from the stable ABI.
Won't there still be a problem of
On 5 Apr, 07:58 pm, mar...@v.loewis.de wrote:
Does this mean new versions of distutils let you build_ext with any C
compiler, instead of enforcing the same compiler as it has done
previously?
No, it doesn't. distutils was considered frozen, and changes to it to
better support the ABI where
Would it be reasonable to begin supporting Visual Studio 2010 for Windows
builds of 3.3? I now have a personal interest in this happening for some
stuff at work, and there's been a lot of questions in the last few months
about when we'll support it coming from python-list, #python-dev, and in
Am 04.04.2011 22:38, schrieb Brian Curtin:
Would it be reasonable to begin supporting Visual Studio 2010 for
Windows builds of 3.3?
Interesting question. The following concerns have played a role in the
past:
- depending on the timing of the next VS release, Python may actually
want to skip
On Mon, 04 Apr 2011 23:40:33 +0200
Martin v. Löwis mar...@v.loewis.de wrote:
- users have expressed concerns that they constantly need to upgrade
VS releases when developing for Python.
Isn't that kind of a misguided argument? It's not Python who decides the
lifecycle of MSVC releases, it's
On 04/04/2011 23:21, Antoine Pitrou wrote:
On Mon, 04 Apr 2011 23:40:33 +0200
Martin v. Löwismar...@v.loewis.de wrote:
- users have expressed concerns that they constantly need to upgrade
VS releases when developing for Python.
Isn't that kind of a misguided argument? It's not Python who
On 4/4/2011 6:43 PM, Michael Foord wrote:
Won't that still be an issue despite the stable ABI? Extensions on
Windows should be linked to the same version of MSVCRT used to compile
Python - and every time we switch version of Visual Studio it is usually
accompanied by a switch in MSVCRT
On 05/04/2011 00:12, Scott Dial wrote:
On 4/4/2011 6:43 PM, Michael Foord wrote:
Won't that still be an issue despite the stable ABI? Extensions on
Windows should be linked to the same version of MSVCRT used to compile
Python - and every time we switch version of Visual Studio it is usually
19 matches
Mail list logo
