onvenient, I have written this (draft)
function:
http://pastebin.com/w5Ejz3Jt
As an example:
data_files=find_data_files({
'': ['locale/*/LC_MESSAGES/*.mo'],
'/tmp/bin': ['tools/*']
}),
> [...]
Regards Manlio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I have find an inconstistency when using the pkg_resources module with
namespace packages.
I'm using setuptools 0.6c11-py2.5.egg
Here is an interactive session:
>>> import pkg_resources
>>> dist = pkg_resources.Requirement.parse('wsgix')
>>> di
like: v1.8.1.301.ga0df26f
It seems that this versioning scheme is not compatible with PEP 386 "new
versioning scheme". Is this true?
Thanks Manlio Perillo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Usi
m curious to know how many Python projects use the config command and
the Autoconf like API.
> [...]
Regards Manlio Perillo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlEGv3EACgkQscQJ
plement an "improved" build_ext command, that will
use options from the config command, as default values.
[1] a better solution is to have the configure method return a
dictionary, but it is more verbose
Feedback is appreciated.
Thanks Manlio Perillo
-BEGIN PGP SIGNATURE---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
It seems I'm having some trobles with setuptools and namespace packages
under Debian Squeeze and Python 2.6.
One thing to say about Python 2.6 on Debian Squeeze is that "local"
packages are installed under /usr/local/lib/python2.6/dist-packages/.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 18/11/2010 17:09, P.J. Eby ha scritto:
> At 04:51 PM 11/18/2010 +0100, Manlio Perillo wrote:
>> Now, I read that this is a Debian policy: for some reasons they force me
>> to use distribute instead setuptools.
>
> Have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 18/11/2010 18:04, Barry Warsaw ha scritto:
> On Nov 18, 2010, at 05:23 PM, Manlio Perillo wrote:
>
>> I usually build Python packages by myself (and often I use virtualenv),
>
> FWIW, virtualenv on Debian has a --setu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 18/11/2010 17:09, P.J. Eby ha scritto:
> At 04:51 PM 11/18/2010 +0100, Manlio Perillo wrote:
>> Now, I read that this is a Debian policy: for some reasons they force me
>> to use distribute instead setuptools.
>
> Have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 18/11/2010 17:08, Tres Seaver ha scritto:
> On 11/18/2010 10:51 AM, Manlio Perillo wrote:
>> No, this is not a flame.
>
>> I'm on Debian Squeeze and I noticed this strange thing:
>
> [setuptools is an alias for sitr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
No, this is not a flame.
I'm on Debian Squeeze and I noticed this strange thing:
$sudo easy_install -U setuptools
install_dir /usr/local/lib/python2.6/dist-packages/
Searching for distribute
Reading http://pypi.python.org/simple/distribute/
Reading h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 04/11/2010 22:01, Alan Franzoni ha scritto:
> On 11/4/10 7:25 PM, Manlio Perillo wrote:
>>> What specific problem are you trying to address?
>>
>>
>> Distribute a Python package on Windows.
>>
>> Suppose
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 04/11/2010 18:16, Alan Franzoni ha scritto:
> On 11/4/10 5:53 PM, Manlio Perillo wrote:
>> For a project using Qt I was unable to use py2exe, and I was unable to
>> understand how to use PyInstaller (!).
>
> That's qu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 04/11/2010 16:52, Alan Franzoni ha scritto:
> On Wed, Nov 3, 2010 at 9:23 PM, Manlio Perillo
> wrote:
>> Hi.
>
> Ciao Manlio!
>
Ciao Alan!
>> Basically, the idea is to build a setuptools distribution format that,
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I'm pleased to announce the eggbuild package.
This is a proof of concept for some ideas I have in mind for Python
packages distribution.
The package name, the implemented setuptools command names and the API
are unstable, and may change in the f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
In many of my projects I add a check for the Python version being used,
like:
if sys.version_info < (2, 6):
raise SystemExit('xxx requires Python 2.6 or higher.')
I think it would be better to specify this requirement as a
`python_requires`
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 13/09/2010 17:43, P.J. Eby ha scritto:
> At 02:03 PM 9/13/2010 +0200, Manlio Perillo wrote:
>> The simplest solutions are:
>> * use py2exe or pyinstaller
>>
>> The problem is that there are some issues using them:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 12/09/2010 20:22, P.J. Eby ha scritto:
> At 02:36 PM 9/12/2010 +0200, Manlio Perillo wrote:
> [...]
>
>> It should not be hard to track installed dependencies, as an example
>> using the --record option of easy_install, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 11/09/2010 23:22, P.J. Eby ha scritto:
> At 09:48 PM 9/11/2010 +0200, Manlio Perillo wrote:
>> Is it possible to put required DLLs inside an egg?
>
> Yes, but they have to be adjacent to any Python extensions (.pyd's) that
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 11/09/2010 20:10, P.J. Eby ha scritto:
> At 04:42 PM 9/11/2010 +0200, Manlio Perillo wrote:
>> This is a problem with the installer, since stdout and stderr are fully
>> buffered.
>
> You probably need to pop up some sort
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 11/09/2010 20:10, P.J. Eby ha scritto:
> At 04:42 PM 9/11/2010 +0200, Manlio Perillo wrote:
>> This is a problem with the installer, since stdout and stderr are fully
>> buffered.
>
> You probably need to pop up some sort
cases the post install script will fail, since the compiler or some
library is not available.
This should not happen; the post install script should, instead, check
if in the package download_url there is a bdist_wininst executable,
download it and execute it.
Suggestions are welcome.
Manlio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 10/09/2010 04:13, P.J. Eby ha scritto:
> At 11:46 PM 9/9/2010 +0200, Manlio Perillo wrote:
>> Il 09/09/2010 23:03, P.J. Eby ha scritto:
>> > At 07:37 PM 9/9/2010 +0200, Manlio Perillo wrote:
>> >> I would like to av
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Today I was building a package that must be installed on a Windows
system (I'm on Linux).
I simply did:
python setup.py bdist_inst
and I was expecting that, when executed on the Windows machine, it would
not only install my package, but also all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
P.J. Eby ha scritto:
> [...]
>> >
>> > The -a in -maxd means that you must have either a source distribution
>> > (e.g. an sdist .tgz, svn: link, etc.) or an .egg. It cannot do
>> > .egg-info at the moment (although when it grows PEP 376 support in 0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
P.J. Eby ha scritto:
> At 10:39 PM 5/22/2010 +0200, Manlio Perillo wrote:
>> The trivial solution is of course to not use "develop" command, and to
>> build a normal egg.
>
> Right. The slightly-less-trivial version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
P.J. Eby ha scritto:
> At 05:55 PM 5/22/2010 +0200, Manlio Perillo wrote:
>> What is the reason why a development egg is being skipped?
>
> Because it can't be copied (currently),
And I usually don't need it to be copied
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Reading easy_install documentation I recently discovered the
- --find-links option, and I'm starting to experiment with it in order to
create a tar archive with all the dependencies of a Python package.
This is very useful when I have to deploy a
P.J. Eby ha scritto:
> [...]
>> I want messages to be compiled (using compile_catalog distutils command
>> from babel) in all these cases:
>> 1) create a binary distribution
>> 2) create an egg
>> 3) running the setup using develop command
>>
>>
>> > [...]
> [...]
>> However I noted that running
>>
P.J. Eby ha scritto:
> At 05:53 PM 5/14/2010 +0200, Manlio Perillo wrote:
>> By the way: in order to get messages compiled, should I just subclass
>> build and develop commands?
>
> I don't understand your question.
>
I want messages to be compiled (using compile_c
P.J. Eby ha scritto:
> At 05:08 PM 5/14/2010 +0200, Manlio Perillo wrote:
>> Hi.
>>
>> In a package, I have gettext catalog messages, and I want to compile
>> them when the package is build.
>>
>> I looked at the Mercurial setup.py script, and what it does
Hi.
In a package, I have gettext catalog messages, and I want to compile
them when the package is build.
I looked at the Mercurial setup.py script, and what it does is:
from distutils.command.build import build
build.sub_commands.insert(0, ('build_mo', None))
Is this the correct way?
Thanks
Tres Seaver ha scritto:
> [...]
>> It seems there is a problem:
>> Sun May 2 19:09:07 2010: An error occurred. Please check the server log
>> for more infomation.
>
> Hmm, must be a transient failure: I was able to reach the site just now.
>
http://bugs.python.org/setuptools/issue42
GET /setup
Phillip J. Eby ha scritto:
> At 09:35 AM 5/2/2010, Manlio Perillo wrote:
>> Hi.
>>
>> Currently setuptools only support a ``tag-svn-revision`` option.
>> However I use Mercurial, and I would like to tag hg revisions.
>>
>>
> [...]
>> def t
Sorry for this reply, but it seems I have some problems at receiving
mails from my gmail account.
I have done some more tests and:
* When installing in the system default site directory, namespace
package work as expected
* When installing in a virtual environment (virtualenv
--no-site-packag
Tres Seaver ha scritto:
> Manlio Perillo wrote:
>> Hi.
>
>> Currently setuptools only support a ``tag-svn-revision`` option.
>> However I use Mercurial, and I would like to tag hg revisions.
> [...]
>
>> I don't know if setuptools is still under develo
Hi.
Currently setuptools only support a ``tag-svn-revision`` option.
However I use Mercurial, and I would like to tag hg revisions.
Looking at setuptool sources, it should not hard to add a new
``tag-revision`` option, used, as an example:
--tag-revision=hg
In egg_info command class, then, t
Hi.
I have a package named A, with a subpackage B, and I want to create a
namespace package A.B.C.
In the namespace package setup file I set
namespace_packages=['A', 'A.B'],
and I use declare_namespace in both A/__init__.py and A/B/__init__.py
modules.
However if I:
1) install A package
2) in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I have a package named A, with a subpackage B, and I want to create a
namespace package A.B.C.
In the namespace package setup file I set
namespace_packages=['A', 'A.B'],
and I use declare_namespace in both A/__init__.py and A/B/__init__.py
mod
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
P.J. Eby ha scritto:
> At 08:52 PM 4/26/2010 +0200, Manlio Perillo wrote:
>> However, I would like to put the data in a *sub* project, that is know
>> only to my project setup. Unfortunately this seems to not be possible.
>>
P.J. Eby ha scritto:
> [...]
>> Right now I'm using a shell script that must be manually executed.
>> The data is copied to a test/resources directory.
>>
>> The test directory contains the test suite and it is in the top level
>> directory of the Python project. It is not installed on the system b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
P.J. Eby ha scritto:
> At 12:19 PM 4/23/2010 +0200, Manlio Perillo wrote:
>> Hi.
>>
>> In a project test suite I need some external resources, that must be
>> downloaded from internet.
>>
>> Is this directly supp
Hi.
In a project test suite I need some external resources, that must be
downloaded from internet.
Is this directly supported by setuptools, or it is better if I write an
additional script that does the job?
Thanks Manlio
___
Distutils-SIG maillist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro ha scritto:
> On Mon, Apr 19, 2010 at 20:37, Manlio Perillo
> wrote:
>> Hi.
>>
>> I would like to use support to namespace packages in setuptools, however
>> I have some doubts.
>>
>> * will
Hi.
I would like to use support to namespace packages in setuptools, however
I have some doubts.
* will this feature be supported for future setup tools?
* is it efficient to use?
* any reason why one should not use it?
Thanks Manlio
___
Distutils-SI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have found that easy_install is not very robust against network problems.
$easy_install --version
distribute 0.6.10
Searching for SQLAlchemy==dev
Reading http://pypi.python.org/simple/SQLAlchemy/
Download error: (113, 'No route to host') -- Some p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raphael Ritz ha scritto:
> Manlio Perillo wrote:
> Hi.
>
> I'm starting to use setuptools for my projects and I have a few
> questions.
>
> In my web applications, usually I have some scripts that needs to be
> inst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
P.J. Eby ha scritto:
> At 04:37 PM 2/16/2010 +0100, Manlio Perillo wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> P.J. Eby ha scritto:
>> > At 02:23 PM 2/16/2010 +0100, Manlio Perillo wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
P.J. Eby ha scritto:
> At 02:23 PM 2/16/2010 +0100, Manlio Perillo wrote:
>> Is it possible to declare a custom directory where some of the scripts
>> needs to be installed?
>
> No. However, you can always create a script wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I'm starting to use setuptools for my projects and I have a few questions.
In my web applications, usually I have some scripts that needs to be
installed as cron scripts.
I would like to install them using setuptools, since it is important
that
50 matches
Mail list logo
