[Chandler-dev] Keeping Feed and other parcels out of the end users' binaries

Philippe Bossut pbossut at osafoundation.org
Fri Sep 1 16:51:39 PDT 2006


Hi,

Mike Taylor wrote:
>
> On Sep 1, 2006, at 6:20 PM, Phillip J. Eby wrote:
>
>>>>
>>>> Just as an FYI, running "setup.py register bdist_egg upload" in a 
>>>> project directory will register the project with the Python 
>>>> Cheeseshop and upload an egg.  There is a "long_description" field 
>>>> that can be set in the setup script, and this is uploaded to the 
>>>> project's cheeseshop page.  For example, see setuptools' Cheeseshop 
>>>> page:
>>>>
>>>>     http://cheeseshop.python.org/pypi/setuptools
>>>
[...snip...]
> Very true, I jumped a couple of steps ahead in my reply - what you 
> said above would work fine.
>
> thanks for clarifying my point better than I would have ;)

Agree with both of you: I didn't think about cheeseshop at all. There's 
no point indeed in reinventing the wheel so my point of "this being a 
huge project" (i.e. creating a repository for all downloadable parcels 
that is end users and 3rd party developers friendly...) is indeed moot 
or, even better, solved!

Thanks for reminding me of this PJE.

The temp "Wiki" solution will be adequate during the 0.7alphax time 
frame, waiting for the API to indeed stabilize.

Cheers,
- Philippe


More information about the chandler-dev mailing list