Hi All,
Looks like something weird is happening:
C:\aproject\trunkpython bootstrap.py
snip
C:\aproject\trunkbin\buildout.exe
Getting distribution for 'zc.buildout'.
Getting distribution for 'setuptools'.
Got setuptools 0.6c8.
Got zc.buildout 1.1.1.
C:\aproject\trunkUpgraded:
zc.buildout
Alberto Valverde wrote:
Ian Bicking wrote:
Alberto Valverde wrote:
The usage is pretty straightforward:
eggfreezer -o AllTurbogears2 -f
http://turbogears.org/2.0/downloads/current TurboGears2 tg.devtools
That command will try to satisfy all dependencies for TurboGears2 and
tg.devtools
Ian Bicking wrote:
Alberto Valverde wrote:
Ian Bicking wrote:
Alberto Valverde wrote:
The usage is pretty straightforward:
eggfreezer -o AllTurbogears2 -f
http://turbogears.org/2.0/downloads/current TurboGears2 tg.devtools
That command will try to satisfy all
Alberto Valverde wrote:
[...]
No... which makes binary eggs unusable on Linux. I feel like there was
something else that made binary packages on a Mac unreliable, but I
can't remember. Windows binary eggs generally work fine. This is
discussed some here:
New submission from Dave Peterson [EMAIL PROTECTED]:
It would be convenient to be able to upload pre-built eggs using the 'python
setup.py upload' command as the owner/author of a project may not have machines
available to cover the platforms for which pre-built binaries are desired.
Having
Ian Bicking schrieb:
No... which makes binary eggs unusable on Linux. I feel like there was
something else that made binary packages on a Mac unreliable, but I
can't remember.
For example that fat eggs (i.e. those with binary code for intel and ppc
architecture inlcuded) will not work on
Arlo Belshee wrote:
Also, since setuptools was likely installed automatically for him via the
egg in the cheeseshop, he isn't aware of anything that may be in dev for
setuptools. A new user's likely response is to get frustrated for 15
minutes, then move on to another web framework /
