ZTK package metadatas are inconsistent
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| zope.applicationcontrol |
In Progress
|
Undecided
|
Justin Alan Ryan | ||
| zope.authentication |
In Progress
|
Undecided
|
Justin Alan Ryan | ||
| zope.browser |
Invalid
|
Undecided
|
Justin Alan Ryan | ||
| zope.browsermenu |
Invalid
|
Undecided
|
Justin Alan Ryan | ||
| zope.browserpage |
Invalid
|
Undecided
|
Justin Alan Ryan | ||
| zope.browserresource |
Invalid
|
Undecided
|
Justin Alan Ryan | ||
| zope.catalog |
Fix Released
|
Undecided
|
Justin Alan Ryan | ||
| zope.componentvocabulary |
Invalid
|
Undecided
|
Justin Alan Ryan | ||
| zope.configuration |
Won't Fix
|
Undecided
|
Unassigned | ||
| zope.container |
Invalid
|
Undecided
|
Unassigned | ||
| zope.contentprovider |
Invalid
|
Undecided
|
Unassigned | ||
| zope.copy |
New
|
Undecided
|
Unassigned | ||
| zope.copypastemove |
New
|
Undecided
|
Unassigned | ||
| zope.datetime |
Invalid
|
Undecided
|
Unassigned | ||
| zope.deferredimport |
Fix Released
|
Undecided
|
Unassigned | ||
| zope.deprecation |
Won't Fix
|
Undecided
|
Unassigned | ||
| zopetoolkit-project |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
As in ticket 161824, many aspects of setup.py across packages listed as part of zopetoolkit-project are inconsistent. All now point to zope-dev instead of zope3-dev mailing list, but I observed:
* Some packages have zope3 in keywords. Changed to zope in some cases, but felt after some time it was a sign of a bigger change needed. In addition to changing this to 'zope', perhaps 'ztk' as a keyword makes sense?
* Some packages have catalog metadata such as Language :: Python, which includes Framework :: Zope3. Tres mentioned we would have to request a new Framework entry from the python catalog-sig to list this as "Zope Toolkit", and I wonder, is it possible we want to register as Framework :: BlueBream? Some packages have no catalog metadata at all, so I'd like to determine what we want each to say, and then make them consistent. I'm happy to request a new framework entry.
Possibly there are other inconsistencies which may be found. As this work may need to touch every single package in some way, I feel it's best to focus on general, Janitorial 'make them consistent' in one ticket to minimize the amount of branches / merges necessary to fold this in and move on with life.
Related branches
| Changed in zopetoolkit-project: | |
| assignee: | nobody → Justin Alan Ryan (justizin) |
| Changed in zope.applicationcontrol: | |
| assignee: | nobody → Justin Alan Ryan (justizin) |
| status: | New → In Progress |
| Changed in zope.authentication: | |
| assignee: | nobody → Justin Alan Ryan (justizin) |
| status: | New → In Progress |
| Changed in zope.browser: | |
| assignee: | nobody → Justin Alan Ryan (justizin) |
| status: | New → In Progress |
| Changed in zope.browsermenu: | |
| assignee: | nobody → Justin Alan Ryan (justizin) |
| status: | New → In Progress |
| Changed in zope.browserpage: | |
| assignee: | nobody → Justin Alan Ryan (justizin) |
| status: | New → In Progress |
| Changed in zope.browserresource: | |
| assignee: | nobody → Justin Alan Ryan (justizin) |
| status: | New → In Progress |
| Changed in zope.catalog: | |
| assignee: | nobody → Justin Alan Ryan (justizin) |
| status: | New → In Progress |
| Changed in zope.componentvocabulary: | |
| assignee: | nobody → Justin Alan Ryan (justizin) |
| status: | New → In Progress |
| Justin Alan Ryan (justizin) wrote | #1 |
| Changed in zope.deprecation: | |
| status: | New → Won't Fix |
| Changed in zope.configuration: | |
| status: | New → Won't Fix |
| Tres Seaver (tseaver) wrote | #2 |
| Changed in zopetoolkit-project: | |
| assignee: | Justin Alan Ryan (justizin) → nobody |
| status: | New → Won't Fix |
| Changed in zope.catalog: | |
| status: | In Progress → Fix Released |
| Changed in zope.deferredimport: | |
| status: | New → Fix Released |
| Colin Watson (cjwatson) wrote | #3 |
| Changed in zope.browser: | |
| status: | In Progress → Invalid |
| Colin Watson (cjwatson) wrote | #4 |
| Changed in zope.browsermenu: | |
| status: | In Progress → Invalid |
| Colin Watson (cjwatson) wrote | #5 |
| Changed in zope.browserpage: | |
| status: | In Progress → Invalid |
| Colin Watson (cjwatson) wrote | #6 |
| Changed in zope.browserresource: | |
| status: | In Progress → Invalid |
| Colin Watson (cjwatson) wrote | #7 |
| Changed in zope.componentvocabulary: | |
| status: | In Progress → Invalid |
| Colin Watson (cjwatson) wrote | #8 |
| Changed in zope.container: | |
| status: | New → Invalid |
| Colin Watson (cjwatson) wrote | #9 |
| Changed in zope.contentprovider: | |
| status: | New → Invalid |
| Colin Watson (cjwatson) wrote | #10 |
| Changed in zope.datetime: | |
| status: | New → Invalid |
I abandoned this originally proposed change as someone on IRC pointed out that the keywords and categorization are linked with others' work, and probably should remain for posterity at least.
I still feel that the package metadatas are inconsistent and could use a bit of cleanup, which is why I originally used a broad subject for this bug.
Some packages have no categorization data at all, and while many include at least their main, if not all of their, doctests in the long_description for PyPI, so I'm going to kick out some changesets to make this more consistent.