You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Eight years ago the python packaging landscape was in disarray. There was setuptools, distribute, distutils, distutils2, paver, and pip – with no clear standard on how to build and package python projects. Wheels didn't exist yet, and virtualenv was still new.
Sideboard makes use of paver (and uber still has a bootstrapped distribute_setup.py file), but this is really a vestige of a time long past. We should probably remove pavement.py and replace any pavement tasks that we currently use with console_scripts in setup.py.
This doesn't actually create any value for us – other than presenting a more familiar tool-chain for new developers – so this issue should be a very low-priority. But I wanted to capture it for future reference.
The text was updated successfully, but these errors were encountered:
Eight years ago the python packaging landscape was in disarray. There was setuptools, distribute, distutils, distutils2, paver, and pip – with no clear standard on how to build and package python projects. Wheels didn't exist yet, and virtualenv was still new.
Sideboard makes use of paver (and uber still has a bootstrapped
distribute_setup.py
file), but this is really a vestige of a time long past. We should probably removepavement.py
and replace any pavement tasks that we currently use withconsole_scripts
insetup.py
.This doesn't actually create any value for us – other than presenting a more familiar tool-chain for new developers – so this issue should be a very low-priority. But I wanted to capture it for future reference.
The text was updated successfully, but these errors were encountered: