Edgewall Software

Opened 8 years ago

Last modified 5 years ago

#12288 closed enhancement

Replace easy_install and eggs with pip and wheels — at Initial Version

Reported by: anonymous Owned by:
Priority: normal Milestone: 1.4
Component: general Version:
Severity: normal Keywords: documentation pip wheel
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description

The Trac documentation talks a lot about easy_install and eggs. Presumably when it was written these were the best practices. It seems today using pip and wheels would be much easier and generally preferable.

The Python docs say:

pip is the preferred installer program. Starting with Python 2.7.9, it is included by default with the Python binary installers.

But from the Trac documentation (to someone who is not a Python packaging expert) it is far from clear if this is recommended or even possible with Trac. Some examples:

  • TracInstall lists easy_install before pip, and the pip section is fairly confusing and assumes Linux, Apache, non-SQLite. This page does not mention wheels (the word egg appears six times).
  • TracUpgrade does not mention pip or wheels at all. (easy_install is mentioned four times, egg once.)
  • TracPlugins lists easy_install before pip, and much more often (12 vs. 5). This page does not mention wheels, while the word egg occurs >40 times.
  • TracDev/PluginDevelopment: egg 10, wheel 0. Links to th:wiki:EggCookingTutorial as the tutorial to build plugins.

(And there are many more on other wiki pages.)

Please clarify if this is still the preferred way or just a historical relict nobody has bothered to change yet. Are pip and/or wheels supported and/or even preferred nowadays? Should such old documentation be updated to recommend pip first? Can old easy_install cruft even be removed?

Change History (0)

Note: See TracTickets for help on using tickets.