Mailman 3 February 2004 - Distutils-SIG

fake
by 15090.61304.110929.45684＠aaa.zzz.org 27 Feb '04

27 Feb '04

reply

1 0

data_files and sdist
by Paul Prescod 27 Feb '04

27 Feb '04

Is there a deep reason that the sdist command does not include data_file files by default? Paul Prescod

4 6

Distutils and MinGW with C++
by Seo Sanghyeon 26 Feb '04

26 Feb '04

I want someone to have a look at SF patch 888839 and check it in if it looks fine. It is a one-line patch. This solves a problem mentioned in following threads: http://groups.google.com/groups?th=1978cf9e295b50fb http://groups.google.com/groups?th=935cfbfbb092c48a The first thread suggests linking with libstdc++ or hacking distutils.sysconfig to link with g++, which doesn't feel right. The second thread says linking with libstdc++ hack doesn't work any more with 2.3, because 2.3 'fixed' the problem: it autodetects C++ file and invokes nonexistent 'cc'. Regards,

2 1

Compiling Extensions with Visual Studio 7
by Ju-Lian Kwan 25 Feb '04

25 Feb '04

Hello, I apologize if this is somewhere in the archives, I did a quick scan of the topics over the last while and couldn't find anything. Anyway, as was pointed on somewhere after Googling, that intermixing stuff built with Visual Studio 7 with stuff from VS6 may result in bad things happening, so that's why distutils included with python 2.3 produces a "Python built with VS6, extensions must be built with it too" type message. However, I downloaded a source distribution, went into the PCBUILD dir and rebuilt the lot. I'm using the source tree (with the built binaries moved to appropriate places) as my python installation, but I still get the same message. Does anyone have any idea how I can get around this? It's probably really easy and obvious but I'm not accustomed to building Python from source. Ju-Lian

1 0

mutt-announce@mutt.org: Non-member submission from distutils-sig@python.org
by owner-mutt-announce＠mutt.org 25 Feb '04

25 Feb '04

Your submission to the list has been forwarded to the list owner <owner-mutt-announce(a)mutt.org> for approval because you do not seem to be on that list. If you want to join the list, send email to <Majordomo(a)mutt.org>, with "subscribe mutt-announce" in the message text (not the subject).

1 0

RE: [Distutils] MSVC CRT woes
by Moore, Paul 20 Feb '04

20 Feb '04

From: Mark Hammond >> Just to understand this: will this mean that you have to have VC7 >> in order to build extensions for Python 2.4 and onwards ? > Officially, I think it will. Unofficially, it will remain like it does > today - it *may* work (depending on if you try and use Python API functions > that use FILE objects). IIRC, there used to be a problem of you implemented > objects, as the malloc/free pairs happened in different CRTLs, but I think > that in recent versions the macro-magic means they do match) I believe that mingw will build extensions which work with Python 2.3 and 2.4, because mingw supports both MSVC runtimes. You still have to build the extension using distutils from the appropriate Python version (ie, you need 2 Python versions installed). > A Python API function "PyFile_OpenFile()" would also solve this issue, but > obviously that wouldn't exist in 2.3 or earlier, so doesn't help this > specific case. According to Martin von Loewis, this is a lost cause - mixing runtimes is never OK, even if you don't use "dangerous" functions (like ones which use FILE*). However, in practical terms, I've never generated a problem (although I haven't tried very hard). >> I think it is worthwhile (and have always argued that way) to have one >> distutils version which can create Python distributables for various >> Python versions, including as many older versions as possible. > I believe that is the intent. There is one other small issue I had trying > to do this for win32all, but I will address that later. >> Does the move to VC7 mean that we'll break this strategy with >> Python 2.4 distutils ? > Yes, unless we do as outlined in my mail. I may be misunderstanding what is being discussed here, but I believe that with the move to VC7, you will need the following to build extensions compatible with both Python 2.3 and 2.4: 1. Installed copies of both Python 2.3 and 2.4. 2. EITHER MSVC 6 and 7 (both versions) OR mingw But I am probably missing something, as once you have the 2 versions of Python installed, I don't see the value in using a single shared distutils, rather than the one that comes with each Python. teaching-my-grandmother-to-suck-eggs-ly y'rs Paul.

6 20

Picky Picky...
by Phil Hornby 20 Feb '04

20 Feb '04

Thomas, Okay I have tried to modify the tail a little... I hope that it is now a little less tick-like... My other idea was a Python-in-a-box...but I prefered this... -- Phil "Requirements - what are they I just hack something together that does what I think they want" ;)

2 1

Re: zvzmtwpkplmslevcj
by robert＠softincubator.com 19 Feb '04

19 Feb '04

This is an autoresponder. I'll never see your message.

1 0

information
by suzette_kimball＠usgs.gov 18 Feb '04

18 Feb '04

something is going wrong

1 0

Google affiliate program is the best there is
by Patrick Tucker 17 Feb '04

17 Feb '04

1 0