On 8/16/07, Cliff Wells [EMAIL PROTECTED] wrote:
On Wed, 2007-08-15 at 19:15 +0200, Neil Blakey-Milner wrote:
Or, even better, use virtual-python or workingenv, and never install
moving targets into your core Python library location.
Out of curiosity, what does workingenv offer over the
On 8/15/07, Christoph Haas [EMAIL PROTECTED] wrote:
Morale: never install eggs on a Debian-based system.
Use workingenv when trying out a new version of Pylons, so that you
can delete the entire environment easily. It's also great for
developing an application and trying them out under several
On 8/15/07, Ian Bicking [EMAIL PROTECTED] wrote:
Yeah; weird stuff with site-packages or easy-install.pth, perhaps?
Doing python -c import pylons; print pylons.__file__ might help debug,
and maybe if you install yolk it'll help explain stuff.
For the (future) record and the next person that
On Wed, Aug 15, 2007 at 09:02:22AM -0400, Matt Feifarek wrote:
On 8/15/07, Ian Bicking [EMAIL PROTECTED] wrote:
Yeah; weird stuff with site-packages or easy-install.pth, perhaps?
Doing python -c import pylons; print pylons.__file__ might help debug,
and maybe if you install yolk
On 8/15/07, Neil Blakey-Milner [EMAIL PROTECTED] wrote:
On 8/15/07, Christoph Haas [EMAIL PROTECTED] wrote:
Morale: never install eggs on a Debian-based system.
Or, even better, use virtual-python or workingenv, and never install
moving targets into your core Python library location.
Ok,
On Aug 15, 10:01 am, Christoph Haas [EMAIL PROTECTED] wrote:
On Wed, Aug 15, 2007 at 09:02:22AM -0400, Matt Feifarek wrote:
On 8/15/07, Ian Bicking [EMAIL PROTECTED] wrote:
Yeah; weird stuff with site-packages or easy-install.pth, perhaps?
Doing python -c import pylons; print
On Wed, Aug 15, 2007 at 02:19:14PM -0400, Matt Feifarek wrote:
On 8/15/07, Neil Blakey-Milner [EMAIL PROTECTED] wrote:
On 8/15/07, Christoph Haas [EMAIL PROTECTED] wrote:
Morale: never install eggs on a Debian-based system.
Or, even better, use virtual-python or workingenv,
On Wed, Aug 15, 2007 at 06:33:33PM -, __wyatt wrote:
On Aug 15, 10:01 am, Christoph Haas [EMAIL PROTECTED] wrote:
On Wed, Aug 15, 2007 at 09:02:22AM -0400, Matt Feifarek wrote:
On 8/15/07, Ian Bicking [EMAIL PROTECTED] wrote:
Yeah; weird stuff with site-packages or
On 8/15/07, Christoph Haas [EMAIL PROTECTED] wrote:
On Wed, Aug 15, 2007 at 06:33:33PM -, __wyatt wrote:
On Aug 15, 10:01 am, Christoph Haas [EMAIL PROTECTED] wrote:
On Wed, Aug 15, 2007 at 09:02:22AM -0400, Matt Feifarek wrote:
On 8/15/07, Ian Bicking [EMAIL PROTECTED] wrote:
Matt Feifarek wrote:
On 8/15/07, *Neil Blakey-Milner* [EMAIL PROTECTED] mailto:[EMAIL
PROTECTED] wrote:
On 8/15/07, Christoph Haas [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Morale: never install eggs on a Debian-based system.
Or, even better, use
On Wed, 2007-08-15 at 19:15 +0200, Neil Blakey-Milner wrote:
Or, even better, use virtual-python or workingenv, and never install
moving targets into your core Python library location.
Out of curiosity, what does workingenv offer over the standard
setuptools way of doing things?
Cliff Wells wrote:
On Wed, 2007-08-15 at 19:15 +0200, Neil Blakey-Milner wrote:
Or, even better, use virtual-python or workingenv, and never install
moving targets into your core Python library location.
Out of curiosity, what does workingenv offer over the standard
setuptools way of
Hello Pylons and Paste folks.
I'm working on a project that is derived from paster create -t
pylons_minimal. It runs great on my development box, but when I try and put
it on another box, I get a traceback that ends in the following:
File
Interesting followup:
running paster create -t pylons_minimal foo on both boxes yields different
results... a recursive diff finds all kinds of things different.
Looks like my eggs are not properly installed, or how else could I be
getting different app skeletons from the same command?
Matt Feifarek wrote:
Interesting followup:
running paster create -t pylons_minimal foo on both boxes yields
different results... a recursive diff finds all kinds of things different.
Looks like my eggs are not properly installed, or how else could I be
getting different app skeletons
For what it's worth, I ran into troubles like this several times
before I began using Ian's excellent workingenv.py [http://
cheeseshop.python.org/pypi/workingenv.py].
It takes an additional step or two for me to setup a new project
(reinstalling pylons mostly), but it has worked wonders for
16 matches
Mail list logo