I've been working with workingenv.py and zope a bit. It offers a very nice fashion of working with zope(constrains python and setuptools to operating in a restricted environment). there are some lumps. you have to call the --home flag when creating the environment. I haven't successful made a zope checkout in to a workingenv itself. those are small potatoes. More pressing is that currently to make this work, you have to hand edit bin/zopectl and bin/runzope like so:: PYTHONPATH="$SOFTWARE_HOME" to: PYTHONPATH="$SOFTWARE_HOME:$PYTHONPATH" Would there be any negative sideeffect to make this change the default in the instance skeleton? It seems like if you've set your PYTHONPATH and start zope, you would expect that path to be available. Anyone object to this going forward? Anyone think this is a bug that should be fixed(on older versions)? comments, suggestions appreciated. -w
On Wed, Sep 27, 2006 at 06:26:49PM -0500, whit wrote:
It seems like if you've set your PYTHONPATH and start zope, you would expect that path to be available.
Indeed.
Anyone object to this going forward? Anyone think this is a bug that should be fixed(on older versions)?
I think it's a bug, but then, I don't recall ever stumbling on it in practice. -- Paul Winkler http://www.slinkp.com
Paul Winkler wrote:
On Wed, Sep 27, 2006 at 06:26:49PM -0500, whit wrote:
It seems like if you've set your PYTHONPATH and start zope, you would expect that path to be available.
Indeed.
Anyone object to this going forward? Anyone think this is a bug that should be fixed(on older versions)?
I think it's a bug, but then, I don't recall ever stumbling on it in practice.
alright... if noone objects, I'm filing this as a bug and making the change. will wait another 24 hours. -w
silence == consent. will proceed as declared. -w whit wrote:
Paul Winkler wrote:
On Wed, Sep 27, 2006 at 06:26:49PM -0500, whit wrote:
It seems like if you've set your PYTHONPATH and start zope, you would expect that path to be available.
Indeed.
Anyone object to this going forward? Anyone think this is a bug that should be fixed(on older versions)?
I think it's a bug, but then, I don't recall ever stumbling on it in practice.
alright... if noone objects, I'm filing this as a bug and making the change.
will wait another 24 hours.
-w
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
http://www.zope.org/Collectors/Zope/2206 is resolved for *nix flavors(sorry for double posting, completely forgot I had posted the bug before). I have no access to a win box so someone else will need do the necessary changes to the bat files in skel(if this sort of thing is even possible on windows). -w whit wrote:
silence == consent. will proceed as declared.
-w
whit wrote:
Paul Winkler wrote:
On Wed, Sep 27, 2006 at 06:26:49PM -0500, whit wrote:
It seems like if you've set your PYTHONPATH and start zope, you would expect that path to be available.
Indeed.
Anyone object to this going forward? Anyone think this is a bug that should be fixed(on older versions)?
I think it's a bug, but then, I don't recall ever stumbling on it in practice.
alright... if noone objects, I'm filing this as a bug and making the change.
will wait another 24 hours.
-w
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
On Mon, Oct 16, 2006 at 11:49:14AM -0500, whit wrote: | http://www.zope.org/Collectors/Zope/2206 is resolved for *nix | flavors(sorry for double posting, completely forgot I had posted the bug | before). I have no access to a win box so someone else will need do the | necessary changes to the bat files in skel(if this sort of thing is even | possible on windows). Of course it is. Just use '%PYTHONPATH%' instead of '$PYTHONPATH'. While on the subject, I had asked about adding $INSTANCE_HOME/lib/python as well. No one seemed to object. Do you mind making this extra change while you're at it? This one should come before everything else in PYTHONPATH. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
Sidnei da Silva wrote:
On Mon, Oct 16, 2006 at 11:49:14AM -0500, whit wrote: | http://www.zope.org/Collectors/Zope/2206 is resolved for *nix | flavors(sorry for double posting, completely forgot I had posted the bug | before). I have no access to a win box so someone else will need do the | necessary changes to the bat files in skel(if this sort of thing is even | possible on windows).
Of course it is. Just use '%PYTHONPATH%' instead of '$PYTHONPATH'.
While on the subject, I had asked about adding $INSTANCE_HOME/lib/python as well. No one seemed to object. Do you mind making this extra change while you're at it? This one should come before everything else in PYTHONPATH.
$INSTANCE_HOME/lib/python:$SOFTWARE_HOME:$PYTHONPATH sounds good to me -w
participants (3)
-
Paul Winkler -
Sidnei da Silva -
whit