On Jun 26, 2006, at 5:54 AM, Martijn Faassen wrote:
Jim Fulton wrote:
[snip]
Adding a call to addsitedir won't accomplish your stated goal of
dropping eggs into lib/python and having them get used. For
addsitedir to have any impact, you have to also manage the .pth
files.
I don't know
Jim Fulton wrote:
[snip]
Adding a call to addsitedir won't accomplish your stated goal of
dropping eggs into lib/python and having them get used. For addsitedir
to have any impact, you have to also manage the .pth files.
I don't know what you mean here. I don't recall managing any .pth
file
Jim Fulton wrote:
>> Jim Fulton wrote:
Concretely, what do you think about making lib/python in a Zope 3.3
instance a site for now (calling site.addsitedir())?
>>>
>>> I think it's a bad idea, mainly because it's too late to make such a
>>> change for 3.3. I tell you what I will do though
On Jun 24, 2006, at 3:38 AM, Philipp von Weitershausen wrote:
Jim Fulton wrote:
Concretely, what do you think about making lib/python in a Zope 3.3
instance a site for now (calling site.addsitedir())?
I think it's a bad idea, mainly because it's too late to make such a
change for 3.3. I tell
Jim Fulton wrote:
>> Concretely, what do you think about making lib/python in a Zope 3.3
>> instance a site for now (calling site.addsitedir())?
>
> I think it's a bad idea, mainly because it's too late to make such a
> change for 3.3. I tell you what I will do though, I'll promise, by
> the end o
Hey Daniel,
Daniel Nouri wrote:
I forgot to mention workingenv[1] yesterday on IRC. It's much easier
than using virtual-python.py. Using workingenv means you can just
"easy_install yourproject" without any further arguments. Of course you
have to take care that the environment is active when
Hi Martijn!
I forgot to mention workingenv[1] yesterday on IRC. It's much easier
than using virtual-python.py. Using workingenv means you can just
"easy_install yourproject" without any further arguments. Of course you
have to take care that the environment is active when you run the Zope
insta