524
Comment:
|
3362
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
Cheese Shop Development |
|
Line 9: | Line 7: |
https://svn.python.org/packages/{trunk,features,branches}. | https://svn.python.org/packages/ (trunk,features,branches) Requests for new Trove categories: Python frameworks with plugins or packages that target the framework can get their own category. The category should only be added *after* such packages exist. Complimentary packages can link to each other from their descriptions, they do not need a category to link them together; only when packages are provided by different people does a category need to be created. To ask for a category email catalog-sig@python.org. |
Line 18: | Line 26: |
== XML-RPC Interface == The Cheese Shop has an XML-RPC interface. See CheeseShopXmlRpc for details. == TO-DO list == * [https://python.domainunion.de/peps/pep-0345.html PEP for metadata 1.2] -- not finished and needs more catalog-sig discussion) * edit [https://python.domainunion.de/peps/pep-0243.html PEP 243] to reflect reality * auto-generate download_urls for package uploads * command-line tool to query pypi and fetch entries * DOAP support * documented procedures for "taking over" entries should the original owner of the entry go away (and any required system support) * better searching (eg. single search box on the front page) * tooltips for field labels * change notification emails * auto-compute [https://pycheesecake.org Cheesecake] scores * moderated user reviews and ratings * strip leading whitespace from description before ReST * "what's related" using classifiers and possibly user-supplied information Something that's been requested, but needs much more thought and analysis to see whether it causes any problems: the ability to treat project names and versions as case-insensitive, while removing extraneous characters (as in pkg_resources.safe_name()) for purposes both of searching and determining name uniqueness when registering. == Development Environment Hints == Before restoring database, "pypi" role must exists: createuser pypi These are notes so we can remember how to dump / restore the packages database: pg_dump -Fc -b packages >packages-20060706.dump createdb packages pg_restore -O -d packages -Fc packages-20060706.dump Ask RichardJones if you need a database dump. PageTemplates are obtained from: svn co svn://svn.zope.org/repos/main/zope.pagetemplate/trunk zope. pagetemplate svn co svn://svn.zope.org/repos/main/zope.tal/trunk zope.tal svn co svn://svn.zope.org/repos/main/zope.interface/trunk zope.interface svn co svn://svn.zope.org/repos/main/zope.i18nmessageid/trunk zope.i18nmessageid svn co svn://svn.zope.org/repos/main/zope.tales/trunk zope.tales We also need to install ez_setup and docutils. Then go ahead and edit pypi.ini and this line in pypi.py: cfg = config.Config('/tmp/pypi.ini', 'webui') if your config.ini isn't in /tmp/pypi.ini. You can leave it as 'config.ini' if it's in the same directory as pypi.py. |
This page documents the development of the Python Cheese Shop:
The PyPI (packages index, Cheese Shop web interface) code resides in SVN at:
https://svn.python.org/packages/ (trunk,features,branches)
Requests for new Trove categories:
- Python frameworks with plugins or packages that target the framework can get their own category. The category should only be added *after* such packages exist. Complimentary packages can link to each other from their descriptions, they do not need a category to link them together; only when packages are provided by different people does a category need to be created. To ask for a category email
Patches and bug reports should be submitted to:
Discussion about the Cheese Shop should be had on the Catalog SIG mailing list:
XML-RPC Interface
The Cheese Shop has an XML-RPC interface. See CheeseShopXmlRpc for details.
TO-DO list
[https://python.domainunion.de/peps/pep-0345.html PEP for metadata 1.2] -- not finished and needs more catalog-sig discussion)
edit [https://python.domainunion.de/peps/pep-0243.html PEP 243] to reflect reality
- auto-generate download_urls for package uploads
- command-line tool to query pypi and fetch entries
- DOAP support
- documented procedures for "taking over" entries should the original owner of the entry go away (and any required system support)
- better searching (eg. single search box on the front page)
- tooltips for field labels
- change notification emails
auto-compute [https://pycheesecake.org Cheesecake] scores
- moderated user reviews and ratings
- strip leading whitespace from description before ReST
- "what's related" using classifiers and possibly user-supplied information
Something that's been requested, but needs much more thought and analysis to see whether it causes any problems: the ability to treat project names and versions as case-insensitive, while removing extraneous characters (as in pkg_resources.safe_name()) for purposes both of searching and determining name uniqueness when registering.
Development Environment Hints
Before restoring database, "pypi" role must exists:
- createuser pypi
These are notes so we can remember how to dump / restore the packages database:
pg_dump -Fc -b packages >packages-20060706.dump createdb packages pg_restore -O -d packages -Fc packages-20060706.dump
Ask RichardJones if you need a database dump.
PageTemplates are obtained from:
- svn co svn://svn.zope.org/repos/main/zope.pagetemplate/trunk zope. pagetemplate svn co svn://svn.zope.org/repos/main/zope.tal/trunk zope.tal svn co svn://svn.zope.org/repos/main/zope.interface/trunk zope.interface svn co svn://svn.zope.org/repos/main/zope.i18nmessageid/trunk zope.i18nmessageid svn co svn://svn.zope.org/repos/main/zope.tales/trunk zope.tales
We also need to install ez_setup and docutils.
Then go ahead and edit pypi.ini and this line in pypi.py:
- cfg = config.Config('/tmp/pypi.ini', 'webui')
if your config.ini isn't in /tmp/pypi.ini. You can leave it as 'config.ini' if it's in the same directory as pypi.py.