Mailman 3 April 2012 - Distutils-SIG

proper use of use_2to3 with Distribute's test
by Chris Jerdonek 07 Apr '12

07 Apr '12

I have a question regarding the proper use of the use_2to3 feature of Distribute's test, as described here: [1] http://packages.python.org/distribute/python3.html#distribute-as-help-durin… My tests run correctly under Python 2.7 when running the following: python setup.py test However, when I switch to Python 3, I get a syntax error when running this command. The syntax error occurs in a module in a subdirectory of my working directory called "tests". Modules in this directory don't seem to be converted to Python 3 when using the "use_2to3" keyword argument. When I manually convert everything to Python 3 using the following, I am able to run unit tests without that same syntax error: 2to3 --write --nobackups --no-diffs . What is the proper way to tell setup() which files to convert to Python 3? Below is the relevant portion of my call to setup(): setup(name='pystache', ... packages=['pystache'], test_suite = 'tests', ) It might be worth expanding the documentation in the link [1] above with the additional information that an answer to my question will provide. Thanks, --Chris

1 1

Creating msi of Python 3.2 app with custom attributes
by Cesar Covarrubias 05 Apr '12

05 Apr '12

Hello, I am working on creating an msi installer from our Python 3.2 application. I would like the installer to allow me to define a default installation path and to create shortcuts to the Start Menu and/or the Desktop. Ideally, we would like to give the user the option to specify if they would like the to install the shortcuts, but this is not required. Default behavior is to install the shortcuts. I have a setup.py that generates the msi with the default path but I can't seem to figure out how to get it to create the shortcuts. Do note that I have looked at http://docs.python.org/distutils/builtdist.html but that doesn't have expanded documentation. Any suggestions or links to documentation would greatly be appreciated. -- Very Respectfully, Cesar Covarrubias

1 0

using pip to install an specific, older version
by Chris Jerdonek 04 Apr '12

04 Apr '12

Hi, I'm trying to use pip to install an older, specific version of a package in PyPI (specifically simplejson v2.0.9): http://pypi.python.org/pypi/simplejson/2.0.9 I've tried a few variations of the syntax below, but it always seems to install the newest version (v2.5.0). I don't know if this is an issue with simplejson, how I'm using pip, or something else. Based on the below, can anyone say why it's not working and how to correct the behavior? Thanks, --Chris > sudo pip freeze -E /opt/local/bin/python nose==1.1.2 > sudo pip install -E /opt/local/bin/python 'simplejson<2.1.0' Downloading/unpacking simplejson<2.1.0 Running setup.py egg_info for package simplejson Installing collected packages: simplejson Running setup.py install for simplejson File "/opt/local/lib/python2.4/site-packages/simplejson/encoder.py", line 398 if (not _bigint_as_string or ^ SyntaxError: invalid syntax Successfully installed simplejson Cleaning up... > sudo pip freeze -E /opt/local/bin/python nose==1.1.2 simplejson==2.5.0 > python -V Python 2.4.6 > which python /opt/local/bin/python > which pip /usr/local/bin/pip

2 4

Buildout: adding a link to a compiled library: uno
by Alessandro Dentella 04 Apr '12

04 Apr '12

Hi, I have many web projects that depend on 'uno' component of openoffice to prepare pdf. I don't really need to compile it inside my buildout env. I'm not really inclined to do that as I know dev and deply is always in an environment with a working system 'uno' package. Under virtualenv all I do is to add 2 symlinks to uno.py and unohelp.py to the site-packages directory. Which is the best way to accomplish a simple setup as this one under buildout? thanks in advance sandro *:-) -- Sandro Dentella *:-) http://www.reteisi.org Soluzioni libere per le scuole http://sqlkit.argolinux.org SQLkit home page - PyGTK/python/sqlalchemy

4 5

Strange warnings from package_index?
by Erik Bray 03 Apr '12

03 Apr '12

Hello, A user of one of my packages came to me the other day with a strange problem that I've never seen before, and have thus far been unable to reproduce. I was wondering if anyone here had any idea about it. When he runs setup.py build on my package, it immediately outputs: $ python setup.py build Not found: /institute/software_hardware/pyraf/favicon.ico Not found: /resources/styles/style.css Not found: /resources/styles/IEstyle.css Not found: /resources/styles/print.css Not found: /resources/styles/mobile.css Not found: /institute/software_hardware/pyraf/localStyle.css Not found: /institute/software_hardware/pyraf/software_hardware Not found: /institute/employment Not found: /jwst Not found: /institute/newsletter Not found: /institute/annual-reports Not found: /institute/atlast Not found: /institute/sd Not found: /institute/Copyright Not found: /institute/help.html ... Followed by the normal build output, which proceeds without any other problems. All those paths are paths on my company's website. This package has a setup_requires dependency which in turn contains dependency_links=['http://stsdas.stsci.edu/download/packages'] in its setup.py, where http://stsda.stsci.edu/download/packages is a local package repository we have for some of our dependencies. It looks like what's happening is that the PackageIndex is finding links on the site *above* the root of the package index, and then searching for local files with the same path? As I understand the PackageIndex code shouldn't follow links that go above the root of the package index site. So I don't know why it's doing this, and can't reproduce the behavior. For what it's worth, the user has distribute installed (though I'm waiting to find out what version), and is using Python 3.2. Any ideas? Thanks, Erik

1 0

Distutils on windows with mingw, messed up includes?
by Kevin Kunzmann 03 Apr '12

03 Apr '12

Hi, I am trying to wrap some c++ library using distutils and swig. So I started with some simple example files and got a faculty function wrapped and runing in ipython. When doing the same with this one: here is the .cpp: #include "jcnError.h" jcnError::jcnError(const string& message, const ErrorType& errorType) : std::runtime_error(message), mErrorMessage(message), mErrorType(errorType) { } const char* jcnError::what(void) const throw() { return std::runtime_error::what(); } jcnError::~jcnError(void) throw() { } here is the header: #pragma once #include <iostream> #include <string> #include <stdexcept> using namespace std; #define jcn_DEBUG /**< If this is defined more error messages will be thrown */ /** * Internal type of error */ enum ErrorType { WARNING, EXCEPTION, }; /** * @class jcnError * @author Jan C. Neddermeyer * @brief jcnError is inherited from the std error class runtime_error */ class jcnError : public runtime_error { public: /** * Constructor * @param message error message, should provide detailed information where and why an error has been thrown * @param errorType optional error type */ jcnError(const string& message, const ErrorType& errorType = EXCEPTION); /** * @return error message, corresponds to the what() method in runtime_error */ virtual const char* what(void) const throw(); /** * @return error message as std::string */ inline const string GetMessage(void) const {return mErrorMessage;}; /** * @return error type */ inline const ErrorType GetErrorType(void) const {return mErrorType;}; /** * Destructor */ ~jcnError(void) throw(); private: string mErrorMessage; /**< error message */ ErrorType mErrorType; /**< error type */ }; here the bpe.i: %module bpetest %{ #include "jcnError.h" %} and finally the setup.py: import distutils from distutils.core import setup, Extension module=Extension('_bpetest',sources=['bpe.i','jcnError.cpp'],include_dirs=['C:/users/kevin/Desktop/bpe_demo/src']) setup(name="bpetest", version="3.2", ext_modules=[module]) I get an error "iostream: No such file or directory". What's the problem? Does distutils get confused by all the virtuals? The error is raised on the very first include line of the headerfile "#include <iostream>" . Thanks, Kevin

1 0

[buildout] branches languishing? (site-packages and distutils scripts)
by Chris Withers 02 Apr '12

02 Apr '12

Hi All, I'm wondering what the state of play is with the following branches: reinout-scripts gary-4-include-site-packages What more needs to happen for these to get merged to trunk and a release made? cheers, Chris

10 28

python file naming...
by Rob Healey 02 Apr '12

02 Apr '12

Greetings: I have python files in my svn repository that I am trying to write my setup.py file for, but I am having problems with. Could someone help me please? I have a file like: /home/Frog/geps0042/gramps/plugins/records.gpr.py, and my setup file errors with: /home/Frog/geps0042/gramps/plugins/records/gpr error: directory does not exist! Would you be able to help me with it??? It is a plugin registration file so it must remain as it is... -- Sincerely yours, Rob G. Healey

3 2

Buildout & develop-eggs troubles
by Alessandro Dentella 01 Apr '12

01 Apr '12

Hi, I'm trying buildout but I'm having a hard time trying to understand the logic of develop-egg. I tested both mr.developer recepy and gp.csvdevelop and I stumbled on the same problem, so I guess I'm misunderstanding something. I want to add a development repository named jumbo-core that contains several 1^ level packages (and a correct setup.py), one of which is 'jumbo', I get to the point that: 1. source is added to ./dev/jumbo-core 2. an egg-link is added to develop-eggs/jumbo-core.egg-link pointing to the correct path where the hg repository is checked out, but that path is not added to the sys.path. My configuration is as follows:: [buildout] develop = . parts = python scripts test ipython extensions = gp.vcsdevelop develop-dir = ./dev vcs-extend-develop = hg+${thunder:jumbonew}/jumbo-core#egg=jumbo-core [python] recipe = zc.recipe.egg interpreter = python eggs = lunar Adding 'jumbo' to eggs directive raises the error: "Couldn't find index page for 'jumbo' (maybe misspelled?)" If I add dev/jumbo-core to develop option I get the message:: Skipping 'hg+/misc/src/hg/thunder/jumbo-new/jumbo-core#egg=jumbo-core'. Package is already in the develop option but dev/jumbo-core is not added to the sys.path. Any hint is appreciated. TIA sandro *:-) -- Sandro Dentella *:-) http://www.reteisi.org Soluzioni libere per le scuole http://sqlkit.argolinux.org SQLkit home page - PyGTK/python/sqlalchemy

2 2