Hello, An full-egg zope 3.4 buildout installed with zopeproject tells me the zope version is 3.3.1 (in /++etc++process/): - I have a fully eggified zope 3.4 installed with zopeproject. - I also have a zope 3.3.1 installed on the system python. When I start the 3.4 full-egg instance, I've discovered that zope.app.applicationcontrol.zopeversion tries to reach zope/app/version.txt to determine the major zope version. Since version.txt does not seem to be included in any egg, it fallbacks to the system zope installed. Where is the bug: zopeversion? zopeproject? a missing egg for zope.app itself? Christophe
Christophe Combelles wrote:
Hello,
An full-egg zope 3.4 buildout installed with zopeproject tells me the zope version is 3.3.1 (in /++etc++process/):
- I have a fully eggified zope 3.4 installed with zopeproject. - I also have a zope 3.3.1 installed on the system python.
When I start the 3.4 full-egg instance, I've discovered that zope.app.applicationcontrol.zopeversion tries to reach zope/app/version.txt to determine the major zope version.
Since version.txt does not seem to be included in any egg, it fallbacks to the system zope installed.
"system zope"? It seems like you have a globally available Zope installation. This will obviously confuse any *local* sandbox, such as the one created with zopeproject. Make sure you don't have any Zope libraries on your standard PYTHONPATH.
On Nov 26, 2007, at 2:28 PM, Philipp von Weitershausen wrote:
Christophe Combelles wrote:
Hello, An full-egg zope 3.4 buildout installed with zopeproject tells me the zope version is 3.3.1 (in /++etc++process/): - I have a fully eggified zope 3.4 installed with zopeproject. - I also have a zope 3.3.1 installed on the system python. When I start the 3.4 full-egg instance, I've discovered that zope.app.applicationcontrol.zopeversion tries to reach zope/app/ version.txt to determine the major zope version. Since version.txt does not seem to be included in any egg, it fallbacks to the system zope installed.
"system zope"? It seems like you have a globally available Zope installation. This will obviously confuse any *local* sandbox, such as the one created with zopeproject. Make sure you don't have any Zope libraries on your standard PYTHONPATH.
Wouldn't it make sense if zopeproject didn't include system python in PYTHONPATH at all? /Tim
Previously TIm Terlegård wrote:
On Nov 26, 2007, at 2:28 PM, Philipp von Weitershausen wrote:
Christophe Combelles wrote:
Hello, An full-egg zope 3.4 buildout installed with zopeproject tells me the zope version is 3.3.1 (in /++etc++process/): - I have a fully eggified zope 3.4 installed with zopeproject. - I also have a zope 3.3.1 installed on the system python. When I start the 3.4 full-egg instance, I've discovered that zope.app.applicationcontrol.zopeversion tries to reach zope/app/ version.txt to determine the major zope version. Since version.txt does not seem to be included in any egg, it fallbacks to the system zope installed.
"system zope"? It seems like you have a globally available Zope installation. This will obviously confuse any *local* sandbox, such as the one created with zopeproject. Make sure you don't have any Zope libraries on your standard PYTHONPATH.
Wouldn't it make sense if zopeproject didn't include system python in PYTHONPATH at all?
No. Wichert. -- Wichert Akkerman <wichert@wiggy.net> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple.
Philipp von Weitershausen a écrit :
Christophe Combelles wrote:
Hello,
An full-egg zope 3.4 buildout installed with zopeproject tells me the zope version is 3.3.1 (in /++etc++process/):
- I have a fully eggified zope 3.4 installed with zopeproject. - I also have a zope 3.3.1 installed on the system python.
When I start the 3.4 full-egg instance, I've discovered that zope.app.applicationcontrol.zopeversion tries to reach zope/app/version.txt to determine the major zope version.
Since version.txt does not seem to be included in any egg, it fallbacks to the system zope installed.
"system zope"? It seems like you have a globally available Zope installation. This will obviously confuse any *local* sandbox, such as the one created with zopeproject. Make sure you don't have any Zope libraries on your standard PYTHONPATH.
Then how is the major zope version defined? Is there any zope/app/version.txt file possibly available for an egg-based installation? Does it even make a sense to define a zope version in that case? Or should version.txt/zopeversion use some version number provided by the KGS? Christophe
participants (4)
-
Christophe Combelles -
Philipp von Weitershausen -
TIm Terlegård -
Wichert Akkerman