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
___
On Tue, Apr 20, 2010 at 12:07 AM, Manlio Perillo
manlio_peri...@libero.it wrote:
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
On Apr 21, 2010, at 05:37 PM, Baiju M wrote:
On Tue, Apr 20, 2010 at 12:07 AM, Manlio Perillo
manlio_peri...@libero.it wrote:
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
On Wed, Apr 21, 2010 at 2:14 PM, Barry Warsaw ba...@python.org wrote:
On Apr 21, 2010, at 05:37 PM, Baiju M wrote:
On Tue, Apr 20, 2010 at 12:07 AM, Manlio Perillo
manlio_peri...@libero.it wrote:
Hi.
I would like to use support to namespace packages in setuptools, however
I have some doubts.
Manlio Perillo wrote:
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?
I have heard that it is slow if you're operating on NFS, as it causes
lots more
At 10:20 AM 4/16/2010 +0200, Luigi GMail wrote:
Therefore instead of making an egg file, easy_install should
simply run `python setup.py install`. Do you know whether this is
possible? Maybe using a different tool instead of easy_install?
The 'pip' tool does this.
Last time we've mentioned this pep on Python-dev, Martin said he would
do its implementation.
Therefore, I am not sure what's the state on his side,.. cc'ing him
Unfortunately, I haven't made any progress - I still *plan* to do it
before the 3.2 betas, though. Contributions are welcome, of
On Apr 21, 2010, at 08:45 PM, Martin v. Löwis wrote:
Last time we've mentioned this pep on Python-dev, Martin said he would
do its implementation.
Therefore, I am not sure what's the state on his side,.. cc'ing him
Unfortunately, I haven't made any progress - I still *plan* to do it
before
On Mon, Apr 19, 2010 at 20:37, Manlio Perillo manlio_peri...@libero.it wrote:
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?
All of Zope and Plone uses it all the time. Trust us, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro ha scritto:
On Mon, Apr 19, 2010 at 20:37, Manlio Perillo manlio_peri...@libero.it
wrote:
Hi.
I would like to use support to namespace packages in setuptools, however
I have some doubts.
* will this feature be supported for
At 09:26 PM 4/21/2010 +0200, Manlio Perillo wrote:
But I do not want to use a feature that it is here for compatiblity
only, in a new project.
Python itself has supported namespace packages through a stdlib
utility since Python 2.3, and special import mechanism support has
been proposed for
On Tue, Apr 20, 2010 at 3:37 AM, Manlio Perillo
manlio_peri...@libero.it wrote:
* will this feature be supported for future setup tools?
* is it efficient to use?
It is slower than conventional packages import. I still don't
understand the whole implementation well, but I think there is an
At 10:18 AM 4/22/2010 +0900, David Cournapeau wrote:
One problem with the setuptools implementation is
that several packages sharing the same namespace have files in common,
If that were actually true (it isn't), then it would be considered a
bug in setuptools.
When you build a package for
13 matches
Mail list logo
