On Fri, 2008-04-11 at 22:00 -0700, Mike Orr wrote:
On Fri, Apr 11, 2008 at 8:55 PM, Cliff Wells [EMAIL PROTECTED] wrote:
The method I've been using is documented here:
http://peak.telecommunity.com/DevCenter/EasyInstall#administrator-installation
I'd like to add, that except for
On Fri, 2008-04-11 at 22:00 -0700, Mike Orr wrote:
On Fri, Apr 11, 2008 at 8:55 PM, Cliff Wells [EMAIL PROTECTED] wrote:
The method I've been using is documented here:
http://peak.telecommunity.com/DevCenter/EasyInstall#administrator-installation
I'd like to add, that except for
On Sat, Apr 12, 2008 at 10:12 AM, Cliff Wells [EMAIL PROTECTED] wrote:
Virtualenv, although it's not part of the stdlib, is straightforward
and self-contained. You don't have to modify the system Python
library to use it, so I don't see why you consider it incompatible
with your old
On Sat, 2008-04-12 at 18:08 -0700, Mike Orr wrote:
On Sat, Apr 12, 2008 at 10:12 AM, Cliff Wells [EMAIL PROTECTED] wrote:
Virtualenv, although it's not part of the stdlib, is straightforward
and self-contained. You don't have to modify the system Python
library to use it, so I
On Sat, 2008-04-12 at 16:51 -0500, Ian Bicking wrote:
In a virtualenv context you wouldn't have had any problem. So... I can
only say that future people will not have this problem, but there's
nothing that can be done about your problem. Except for you to update
the #! lines, which
On Sat, Apr 12, 2008 at 6:44 PM, Cliff Wells [EMAIL PROTECTED] wrote:
virtualenv is very much meant to keep working code working, and I think
it does that. So there is a current answer to that problem.
Yes, I'm turning around on virtualenv. Unfortunately there's not a lot
to be done
Hi
Pylons + WebOb - Documentation
Thanks
Madhu Alagu
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send email to pylons-discuss@googlegroups.com
To unsubscribe
