Commits

Author Commit Message Labels Comments Date
tarek
fixed the forbidden access problem
tarek
rebuilt the eggs
tarek
that is three step
tarek
more details
tarek
shorcut to avoid unecessary work when located in a non-isolated environment
tarek
safer test: will not overwrite an existing file for the test
tarek
fixed a fork bomb when patching non-egg system-wide installation
tarek
more cases from the community
tarek
added a note for manual uninstallation of setuptools.pth
tarek
fixed import test
tarek
test for the bootstrap
tarek
using boostrap.py name for ez_setup.py because that is what it is
tarek
started the re-work on README.txt
tarek
hooked the patching code into setup.py
tarek
not needed
tarek
re-wrote the release.sh script
tarek
fixed distribution key in check_version_conflict. I first thaught it was the #36 issue of setuptools but it's not.
tarek
re-launching when setuptools is faked, and also detecting it's a fake egg to avoid re-patching twice
tarek
populating md5 hashes and default url location
tarek
simplified the installation process. Now faking setuptools eggs. This is making the whole switch simpler for people
tarek
adding the distribute marker here too
tarek
forcing a distribute reinstallation over an existing setuptools one
tarek
fixed typo
tarek
The User-Agent is also changed to Distribute
tarek
making ez_setup removing an existing setuptools distribution out of the way
tarek
cleaning a bit ez_setup.py while reading it
Hanno Schlichting
Update and prepare the ez_setup.py to use distribute instead.
Hanno Schlichting
Added a modified bootstrap.py for zc.buildout
Hanno Schlichting
As suggested by PJE, we want to check in the entry_points.txt file. Otherwise pristine setuptools-less Python installations won't be able to run egg_info or test.
Hanno Schlichting
Whitespace, mark this as the default branch
  1. Prev
  2. Next