Mailman 3 March 2003 - Distutils-SIG

Mixing pure python and extension module and multi platform
by Berthold Höllmann 21 Mar '03

21 Mar '03

Hello, We have a quite large project of some quite stable extension modules and lots of frequently changing python modules. The whole thing works under Solaris and Linux. Both operating systems are accessing the same file tree using NFS. My problem now is that setup on a mixed module installes everything into the system dependent branch of the install directories. It would be nice if there is a simple customizing of the setup procedure to make setup install the extension modules into the system depending branch and the python modules into the system independent branch. Of course I can issue two "setup" commands in the setup.py, but that produces ugly results when it comes to generating binary installation packages. Regards Berthold -- Dipl.-Ing. Berthold Höllmann __ Address: hoel(a)GL-Group.com G / \ L Germanischer Lloyd phone: +49-40-36149-7374 -+----+- Vorsetzen 32/35 P.O.Box 111606 fax : +49-40-36149-7320 \__/ D-20459 Hamburg D-20416 Hamburg **************************************************** Beachten Sie: Wir moechten Sie informieren, dass die E-Mail-Adresse des Germanischen Lloyd sowie unsere Web-Adresse mit Wirkung vom 1. Maerz 2003 auf den Namen gl-group.com umgestellt wurde. Dies bedeutet, dass die bisherige Adresse Kurzzeichen(a)germanlloyd.org durch die neue Adresse Kurzzeichen(a)gl-group.com ersetzt wird. Die Homepage des GL ist kuenftig ueber die Adresse 'http://www.gl-group.com' aufrufbar. Die bisher verwendeten Adressen bleiben für eine Uebergangsfrist erreichbar. **************************************************** Please notice: We would like to inform you that the e-mail address of Germanischer Lloyd as well as our internet address had been changed to gl-group.com with effect from 1st March 2003. This means that the previous address shortmark(a)germanlloyd.org will be replaced by shortmark(a)gl-group.com. From now on the GL homepage can be accessed at the address 'http://www.gl-group.com'. The old addresses remain valid for a transitional period. **************************************************** This e-mail contains confidential information for the exclusive attention of the intended addressee. Any access of third parties to this e-mail is unauthorised. Any use of this e-mail by unintended recipients such as copying, distribution, disclosure etc. is prohibited and may be unlawful. When addressed to our clients the content of this e-mail is subject to the General Terms and Conditions of GL's Group of Companies applicable at the date of this e-mail. GL's Group of Companies does not warrant and/or guarantee that this message at the moment of receipt is authentic, correct and its communication free of errors, interruption etc.

4 10

watch what these girls will do for some free money...so they think
by Jefferson Haley 21 Mar '03

21 Mar '03

Money isn't everything...or so you were told right? Well we bet you that it is! Take a look at these girls who would do absolutely ANYTHING to win over a self made billionaire! http://www.hotxxxpass.net/pass2/ These hardworking girls think it's their lucky day because Max the billionaire suitor has fallen upon them and their wonderful talents! Watch them show themselves off to impress Max! You won't believe what these girls will do to get a piece of Max's pie! http://www.hotxxxpass.net/pass2/ iblsm dgims cmncrgsnssd c

1 0

Installing scripts to multiple directories
by Harald Meland 13 Mar '03

13 Mar '03

Hi, I'm trying to figure out how I can make distutils support installation of scripts to more than one directory, e.g. both <prefix>/bin/ and <prefix>/sbin/. I've found an open bug[1] on this in the Python project on SourceForge, but it's now over a year since the person that bug is assigned to said that he would "look at this". I started by looking through the documentation, but could not find any info on how to extend distutils. Hence, I had a look at how distutils is currently implemented, but I'm still not sure how one is meant to *properly* extend the "install*" feature set. Have anyone done this particular extension already? If not, are there any guidelines on how such an extension ought to be done? [1] Bug id 452144, viewable at http://sourceforge.net/tracker/?func=detail&atid=105470&aid=452144&group_id… -- Harald

3 3

CVS distutils & bdist_wininst
by Jp Calderone 08 Mar '03

08 Mar '03

Hello the list, CVS HEAD of distutils doesn't currently seem to install misc/wininst.exe when "./setup.py install" is run. This causes bdist_wininst to fail with error: /usr/local/lib/python2.2/site-packages/distutils/command/wininst.exe: No such file or directory (It is easily rectified by copying the file into place manually.) I'm not sure if anyone was aware of this, or if it's even appropriate to report CVS bugs to the list. Apologies if this is the wrong forum. Jp -- "There is no reason for any individual to have a computer in their home." -- Ken Olson, President of DEC, World Future Society Convention, 1977 -- up 5 days, 17:59, 10 users, load average: 1.17, 0.91, 0.47

1 0

Pferdemarkt.ws informiert! Newsletter 03/2003 http://www.pferdemarkt.ws
by webmaster＠pferdemarkt.ws 06 Mar '03

06 Mar '03

http://www.pferdemarkt.ws Wir sind in 2003 erfolgreich in des neue \"Pferdejahr 2003 gestartet. Für den schnellen Erfolg unseres Marktes möchten wir uns bei Ihnen bedanken. Heute am 06.03.2003 sind wir gut 2 Monate Online! Täglich wächst unsere Datenbank um 30 Neue Angebote. Stellen auch Sie als Privatperson Ihre zu verkaufenden Pferde direkt und vollkommen Kostenlos ins Internet. Zur besseren Sichtbarmachung Ihrer Angebote können SIe bis zu ein Bild zu Ihrer Pferdeanzeige kostenlos einstellen! Wollen Sie direkt auf die erste Seite, dann können wir Ihnen unser Bonussystem empfehlen. klicken Sie hier: http://www.pferdemarkt.ws/bestellung.html Ihr http://Pferdemarkt.ws Team Klicken Sie hier um sich direkt einzuloggen http://www.Pferdemarkt.ws Kostenlos Anbieten, Kostenlos Suchen! Direkt von Privat zu Privat! Haben Sie noch Fragen mailto: webmaster(a)pferdemarkt.ws

1 0

Possible problem using disutils
by CP Hennessy 05 Mar '03

05 Mar '03

Hi, Sorry if I should be sending this to a different list, but I am not sure if this is a problem with distutils or the package made from distutils. I downloaded from the site http://users.skynet.be/sbi/libxml-python/ the package libxml2-python-2.4.30.win32-py2.1.exe. However when I try to install it there is no directory listed in the "Select python installation to use" dialog ( i.e. the second window). I have Python installed as part of zope. And I even tried to set the env. variable PYTHON_HOME to my python. Python is also in my PATH. Also I cannot manually enter a path in the "Installation Directory:" field of the same window. I'm trying to install this on Windows XP. What can I do ? Thanks CPH

3 5

Re: A question on Python Distutil
by Greg Ward 03 Mar '03

03 Mar '03

On 22 February 2003, Aki Niimura said: > Sorry to bother you. > I have a question on Python Distutil and so far I couldn't find > a solution in the Internet. Please ask Distutils questions on distutils-sig(a)python.org. I'll try to answer, but I have not been heavily involved with the Distutils for quite a while. > My stumbling block was symbloc-link. > In my project working directory, there are several files linked from > another project directory (symblic link). The distutils are mostly ignorant of symbolic links, because they're not portable to Windows or Mac OS. So whatever "tar" does by default with symlinks is the behaviour that you see. > > (ex.) > project_A (the project to be distributed) > setup.py (foo.py, bar.py) > foo.py --> project_B.foo.py > bar.py > > project_B (a project happened to have a useful module) > foo.py > > When I run 'python setup.py sdist', a <project>-<version>.tar.gz was > created but the symbolic link files remained symbolic link. Right, because tar preserves symlinks by default. > My questions are: > (1) Is there any way to ask distutil to treat the file as > a plain file not a link? (hopefully file by file) No, not as far as I know. I can think of two kludges that might work: * create a ZIP file instead of a tarball -- ZIP files cannot represent symlinks, so the symlink will be followed: ./setup.py sdist --formats=zip * write a wrapper for "tar" that forces the "-h" option (which I think makes tar follow symlinks) into the real tar command line > (2) What is the right approach (to your sense) > to setup a project like this? If this is a small, personal project that only you work on, you could make project_A/foo.py a hardlink to ../project_B/foo.py. Hardlinks are best avoided though -- too implicit. But I don't have any other ideas offhand. Greg -- Greg Ward <gward(a)python.net> http://www.gerg.ca/ God is omnipotent, omniscient, and omnibenevolent ---it says so right here on the label.

1 0

python-dev not installed on Unix
by Juergen Hermann 02 Mar '03

02 Mar '03

Hi! This is a VERY common error that traps users regularly: distutils.errors.DistutilsPlatformError: invalid Python installation: unable to open /usr/lib/python2.2/config/Makefile (No such file or directory) Could we extend that error message by a hint on installing the python- dev .rpm/.deb? if sys.platform = "unix": msg += "\nYou probably need to install..." Ciao, Jürgen

2 3

More documentation for setup meta-data
by Richard Jones 01 Mar '03

01 Mar '03

I'm trying to better document the meta-data for the distutils (and hence PyPI). I've added words to the section in the dev doc about meta-data, and would like some feedback before I post the patch to be applied. Sorry, it's in LaTeX form (until someone writes the ReST->python doc converter ;) \subsection{Additional meta-data} \label{meta-data} The setup script may include additional meta-data beyond the name and version. This information includes: \begin{tableiii}{l|l|l|c}{code}% {Meta-Data}{Description}{Value}{Notes} \lineiii{name}{the name of the package}{short string}{(1)} \lineiii{version}{the version of this release}{short string}{(1)(4)} \lineiii{author}{package author's name}{short string}{(2)} \lineiii{author_email}{email address of the package author}{email address}{(2)} \lineiii{maintainer}{package maintainer's name}{short string}{(2)} \lineiii{maintainer_email}{email address of the package maintainer}{email address}{(2)} \lineiii{home_page}{the location of the homepage for the package}{URL}{(1)} \lineiii{description}{a short, summary description of the package}{short string}{} \lineiii{long_description}{a longer description of the package}{long string}{} \lineiii{download_url}{a location where the package may be downloaded}{URL}{(3)} \lineiii{classifiers}{a list of Trove classifiers}{list of strings}{(3)} \end{tableiii} \noindent Notes: \begin{description} \item[(1)] these fields are required \item[(2)] either the author or the maintainer must be nominated \item[(3)] should not be used if your package is to be compatible with Python versions prior to 2.2.3 or 2.3. The list is available from the PyPI website. \item[(4)] it is recommended that versions take the form <major>.<minor>.<patch>[.<sub>] \item["short string"] a single line of text, not more than 200 characters \item["long string"] multiple lines of text \item["list of strings"] see below \end{description} \option{version} encoding is an art in itself. Python packages generally adhere to the version format \em{major.minor.patch}. The major number is 0 for initial, experimental releases of software. It is incremented for releases that represent major milestones in a package. The minor number is incremented when important new features are added to the package. The patch number increments when bug-fix releases are made. Additional trailing version information is sometimes used to indicate sub-releases. These are "a1,a2,...,aN" (for alpha releases, where functionality and API may change), "b1,b2,...,bN" (for beta releases, which only fix bugs) and "pr1,pr2,...,prN" (for final pre-release release testing). Some examples: \begin{description} \item[0.1.0] the first, experimental release of a package \item[1.0.1a2] the second alpha release of the first patch version of 1.0 \end{description} \option{classifiers} are specified in a python list: \begin{verbatim} setup(... classifiers = [ 'Development Status :: 4 - Beta', 'Environment :: Console', 'Environment :: Web Environment', 'Intended Audience :: End Users/Desktop', 'Intended Audience :: Developers', 'Intended Audience :: System Administrators', 'License :: OSI Approved :: Python Software Foundation License', 'Operating System :: MacOS :: MacOS X', 'Operating System :: Microsoft :: Windows', 'Operating System :: POSIX', 'Programming Language :: Python', 'Topic :: Communications :: Email', 'Topic :: Office/Business', 'Topic :: Software Development :: Bug Tracking', ], ... ) \end{verbatim} If you wish to include classifiers in your \file{setup.py} file and also wish to remain backwards-compatible with Python releases prior to 2.2.3, then you can include the following code fragment in your \file{setup.py} before the \code{setup()} call. \begin{verbatim} # patch distutils if it can't cope with the "classifiers" or # "download_url" keywords if sys.version < '2.2.3': from distutils.dist import DistributionMetadata DistributionMetadata.classifiers = None DistributionMetadata.download_url = None \end{verbatim}

5 14

Solution to encoding issue... sorry!
by kevin＠cazabon.com 01 Mar '03

01 Mar '03

I managed to find a solution through a combination of posts... here it is for anyone interested: in setup.cfg (for py2exe section): ######################### packages=encodings force-imports=sitecustomize ######################### and in sitecustomize.py: ######################### import sys, codecs sys.setdefaultencoding("latin1") ######################### Kevin.

1 0