From Fedora Project Wiki
m (Talk:Packaging/Python/Eggs moved to Packaging talk:Python/Eggs: Moving Packaging Pages to Packaging Namespace) |
mNo edit summary |
||
| Line 5: | Line 5: | ||
[[User:jkeating|Jesse Keating]] Do we need to BR python-setuptools-devel, or is python-setuptools sufficient? It seems at least with f11 builds that BR on python-setuptools brings in enough to produce the egginfo | [[User:jkeating|Jesse Keating]] Do we need to BR python-setuptools-devel, or is python-setuptools sufficient? It seems at least with f11 builds that BR on python-setuptools brings in enough to produce the egginfo | ||
=== wiki fix to do === | |||
"...ding: 1. Allowing end users to install eggs not made from rpms or install eggs into their home directories. This is an important feature for people working within a shared hosting environment. 1. Giving python packages an easy way to support plugins. 1. Giving us a way to support multiple versions of a python module for compat libraries." | |||
Please fix up the numbering to use numbered bullets. | |||
Revision as of 08:02, 5 January 2009
The following metadata was found in MoinMoin that could not be converted to a useful value in MediaWiki:
- : Install the egg so that only code that wants this particular version can get it.
Jesse Keating Do we need to BR python-setuptools-devel, or is python-setuptools sufficient? It seems at least with f11 builds that BR on python-setuptools brings in enough to produce the egginfo
wiki fix to do
"...ding: 1. Allowing end users to install eggs not made from rpms or install eggs into their home directories. This is an important feature for people working within a shared hosting environment. 1. Giving python packages an easy way to support plugins. 1. Giving us a way to support multiple versions of a python module for compat libraries."
Please fix up the numbering to use numbered bullets.