[Distutils] RFC : PEP 376 - egg.info

[Tarek Ziadé]

2009/5/3 P.J. Eby <pje at telecommunity.com>:
> At 12:03 PM 5/3/2009 +0200, Tarek Ziadé wrote:
>>
>> The name of each file will have to be normalized: all upper case with
>> no extensions.
>>
>> Any opinions ?
>
> I don't see any point to the normalization.  However, being able to install
> arbitrary files in .egg-info is currently supported by setuptools, and that
> capability is used by e.g. the EggTranslations project.

I am discovering a new callback mechanism here, I am confused.

I was looking at another package last week called "eggtestinfo", that
uses the 'egg_info.writers'
entry point to add package in the egg-info dir created by the egg_info command

So the callbacks are used at installation time and the entry points
only at packaging time,

but I don't understand how EggTranslations is used since it registers
callback only when the code is called

Furtermore, if we provide the ability to fill egg-info with third
party packages registered through
a plugin system, it make sense to prepare it at packaging time to
avoid having to install this third party package
on the target system.

So 'egg_info.writers' + the egg_info command is what makes sense right
now to me.

Tarek

-- 
Tarek Ziadé | http://ziade.org