hi troll
PS: just making sure other people in this list know about it
PSS: please do not reply
On 12/8/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> Ilias Lazaridis wrote:
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org
Ilias Lazaridis wrote:
> I have the following use-case:
>
> within an application, i like to load several plugins from an folder,
> without any user-interaction
>
> app/plugins/pluginone
> app/plugins/plugintwo
>
> the plugins (standard sources prepared for setuptools, coming from svn)
> are a
Phillip J. Eby wrote:
> At 09:22 PM 12/8/2006 +0200, Ilias Lazaridis wrote:
>> Phillip J. Eby wrote:
>>> At 08:24 PM 12/8/2006 +0200, Ilias Lazaridis wrote:
Retrieving a few values directly from the setup.py (instead from an
egg-info) would be fast and without any dependency.
>>> In order
At 09:22 PM 12/8/2006 +0200, Ilias Lazaridis wrote:
>Phillip J. Eby wrote:
> > At 08:24 PM 12/8/2006 +0200, Ilias Lazaridis wrote:
> >> Retrieving a few values directly from the setup.py (instead from an
> >> egg-info) would be fast and without any dependency.
> >
> > In order to invoke run_setup t
Phillip J. Eby wrote:
> At 08:24 PM 12/8/2006 +0200, Ilias Lazaridis wrote:
>> Retrieving a few values directly from the setup.py (instead from an
>> egg-info) would be fast and without any dependency.
>
> In order to invoke run_setup to get the data, you must import, *at absolute
> minimum*:
>
At 08:24 PM 12/8/2006 +0200, Ilias Lazaridis wrote:
>Retrieving a few values directly from the setup.py (instead from an
>egg-info) would be fast and without any dependency.
In order to invoke run_setup to get the data, you must import, *at absolute
minimum*:
distutils
distutils.cmd
distutils.co
Phillip J. Eby wrote:
> At 06:24 PM 12/8/2006 +0200, Ilias Lazaridis wrote:
>> My requirement is to have no additional installation steps after an
>> svn-checkout (or unzip).
>
> Then generate the .egg-info before committing to SVN, or use the "sdist"
> command to create your source zipfiles or t
At 06:24 PM 12/8/2006 +0200, Ilias Lazaridis wrote:
>My requirement is to have no additional installation steps after an
>svn-checkout (or unzip).
Then generate the .egg-info before committing to SVN, or use the "sdist"
command to create your source zipfiles or tarballs, and all will be well.
>
At 03:35 PM 12/8/2006 +0200, Ilias Lazaridis wrote:
>Possibly the class should be named "pkg_resources.Egg" or
>"pkg_resources.EggDistribution" in order to become more descriptive.
No. It's also used to track source distributions being downloaded from
PyPI, and even .win32.exe distributions. It
On Dec 8, 2006, at 5:24 PM, Ilias Lazaridis wrote:
My requirement is to have no additional installation steps after an
svn-checkout (or unzip).
You could include the egg-info in your repository and distribution
archive.
Ronald
smime.p7s
Description: S/MIME cryptographic signature
Phillip J. Eby wrote:
> At 09:03 PM 12/7/2006 +0200, Ilias Lazaridis wrote:
>> This is a special and limited use-case:
>>
>> The eggs do *not* need to be found by other eggs/applications, as they
>> are used only by the application that loads them in.
>
> That's 100% irrelevant.
ok
> There are
Phillip J. Eby wrote:
> At 09:45 PM 12/7/2006 +0200, Ilias Lazaridis wrote:
>> I am a little overworked at this point, but this should be the right
>> direction to enable setuptools to create distributions whilst using the
>> information within setup.py (and without breaking any behaviour):
>
> Th
Phillip J. Eby wrote:
> At 01:42 PM 12/8/2006 +0200, Ilias Lazaridis wrote:
>> are "pkg_resources.Distribution" objects finally the internal
>> representation of eggs?
>
> Yes.
ok.
Possibly the class should be named "pkg_resources.Egg" or
"pkg_resources.EggDistribution" in order to become more
At 01:42 PM 12/8/2006 +0200, Ilias Lazaridis wrote:
>are "pkg_resources.Distribution" objects finally the internal
>representation of eggs?
Yes.
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-si
Phillip J. Eby wrote:
> At 08:57 PM 12/7/2006 +0200, Ilias Lazaridis wrote:
>> ep_map = pkg_resources.EntryPoint.parse_map(dist.entry_points,
>> dist)
> By the way, I missed this line in your email before: you should *not* pass
> dist as the second argument here. That method is looking
At 08:57 PM 12/7/2006 +0200, Ilias Lazaridis wrote:
> ep_map = pkg_resources.EntryPoint.parse_map(dist.entry_points,
>dist)
By the way, I missed this line in your email before: you should *not* pass
dist as the second argument here. That method is looking for a
pkg_resources.Distributi
At 09:45 PM 12/7/2006 +0200, Ilias Lazaridis wrote:
>I am a little overworked at this point, but this should be the right
>direction to enable setuptools to create distributions whilst using the
>information within setup.py (and without breaking any behaviour):
The only way I'll ever support this
Phillip J. Eby wrote:
> At 08:57 PM 12/7/2006 +0200, Ilias Lazaridis wrote:
>>File
>> "C:\prg\py24\lib\site-packages\setuptools-0.6c3-py2.4.egg\pkg_resources.py",
>> line 1829, in load
>> if require: self.require(env, installer)
>
> Yeah, you need to pass 'require=False' to entrypoint.loa
At 09:03 PM 12/7/2006 +0200, Ilias Lazaridis wrote:
>This is a special and limited use-case:
>
>The eggs do *not* need to be found by other eggs/applications, as they
>are used only by the application that loads them in.
That's 100% irrelevant. There are a whole bunch of different ways for you
t
Ilias Lazaridis wrote:
> Phillip J. Eby wrote:
>> At 06:24 PM 12/7/2006 +0200, Ilias Lazaridis wrote:
>>> Looks somehow like this:
> ...
>
>>> How can I create an egg representing object (from the sources/setup.py),
>> >from which I can load the entry-points afterwards, without having to
>>> gener
At 08:57 PM 12/7/2006 +0200, Ilias Lazaridis wrote:
>File
>"C:\prg\py24\lib\site-packages\setuptools-0.6c3-py2.4.egg\pkg_resources.py",
>line 1829, in load
> if require: self.require(env, installer)
Yeah, you need to pass 'require=False' to entrypoint.load(). See:
http://peak.telecommun
Phillip J. Eby wrote:
> At 06:24 PM 12/7/2006 +0200, Ilias Lazaridis wrote:
>> Looks somehow like this:
...
>> How can I create an egg representing object (from the sources/setup.py),
>>from which I can load the entry-points afterwards, without having to
>> generate an egg_info on the file-system?
Phillip J. Eby wrote:
> At 06:24 PM 12/7/2006 +0200, Ilias Lazaridis wrote:
>> Looks somehow like this:
...
>>
>
> That Distribution is a distutils distribution, not a pkg_resources
> distribution.
ok
>> How can I create an egg representing object (from the sources/setup.py),
>>from which I ca
At 06:24 PM 12/7/2006 +0200, Ilias Lazaridis wrote:
>Looks somehow like this:
>
>
>from distutils.core import run_setup
>dist = run_setup( setuppys[0],None,'init')
>print dist
>
>loaded_components = []
>module = []
>
>import pkg_resources
>for name in pkg_resources.get_entry_map(dist,'trac.plugins'
Phillip J. Eby wrote:
> At 03:41 PM 12/7/2006 +0200, Ilias Lazaridis wrote:
>> Is there any documented way to load such a "raw egg" (egg sources
>> without a generated egg-info) into the application, without the need to
>> generate the egg-info?
>
> No. Of course, if you know where the plugin dir
At 03:41 PM 12/7/2006 +0200, Ilias Lazaridis wrote:
>Is there any documented way to load such a "raw egg" (egg sources
>without a generated egg-info) into the application, without the need to
>generate the egg-info?
No. Of course, if you know where the plugin directories are, you can
always run
I have the following use-case:
within an application, i like to load several plugins from an folder,
without any user-interaction
app/plugins/pluginone
app/plugins/plugintwo
the plugins (standard sources prepared for setuptools, coming from svn)
are arranged like this:
pluginone/one
pluginone
27 matches
Mail list logo
