Zope 2.12.2 SyntaxError on installation
Following the guide at http://docs.zope.org/zope2/releases/2.12/INSTALL.html#buildout-instances I get the following error: mg@platonas:~/src/akl-website-z2.12-experiment $ python2.5 bootstrap.py Creating directory '/home/mg/src/akl-website-z2.12-experiment/bin'. Creating directory '/home/mg/src/akl-website-z2.12-experiment/parts'. Creating directory '/home/mg/src/akl-website-z2.12-experiment/develop-eggs'. Generated script '/home/mg/src/akl-website-z2.12-experiment/bin/buildout'. mg@platonas:~/src/akl-website-z2.12-experiment $ time bin/buildout Upgraded: zc.buildout version 1.4.3, setuptools version 0.6c11; restarting. Generated script '/home/mg/src/akl-website-z2.12-experiment/bin/buildout'. Installing instance. Getting distribution for 'Zope2'. src/AccessControl/cAccessControl.c:598: warning: ‘intargfunc’ is deprecated src/AccessControl/cAccessControl.c:599: warning: ‘intargfunc’ is deprecated src/AccessControl/cAccessControl.c:600: warning: ‘intintargfunc’ is deprecated src/AccessControl/cAccessControl.c:606: warning: ‘intargfunc’ is deprecated src/Record/_Record.c:340: warning: ‘intargfunc’ is deprecated src/Record/_Record.c:341: warning: ‘intargfunc’ is deprecated src/Record/_Record.c:342: warning: ‘intintargfunc’ is deprecated File "build/bdist.linux-i686/egg/Zope2/utilities/load_site.py", line 248 body = ("<html><head><title><dtml-var title_or_id></title> ^ SyntaxError: EOL while scanning single-quoted string File "/home/mg/tmp/buildout-eggs/tmprWUwxL/Zope2-2.12.2-py2.5-linux-i686.egg/Zope2/utilities/load_site.py", line 248 body = ("<html><head><title><dtml-var title_or_id></title> ^ SyntaxError: EOL while scanning single-quoted string Got Zope2 2.12.2. which seems to be https://bugs.launchpad.net/zope2/+bug/501265 Then buildout proceeds as if nothing is wrong. Getting distribution for 'zope.app.publication==3.7.0'. Got zope.app.publication 3.7.0. Getting distribution for 'zope.app.form==3.8.1'. Got zope.app.form 3.8.1. Getting distribution for 'zope.viewlet==3.5.0'. Got zope.viewlet 3.5.0. Getting distribution for 'zope.contentprovider==3.5.0'. Got zope.contentprovider 3.5.0. Getting distribution for 'zope.component==3.7.1'. Got zope.component 3.7.1. Getting distribution for 'zLOG==2.11.1'. Got zLOG 2.11.1. Getting distribution for 'tempstorage==2.11.2'. Got tempstorage 2.11.2. Getting distribution for 'Persistence==2.11.1'. Got Persistence 2.11.1. Getting distribution for 'ExtensionClass==2.11.3'. Got ExtensionClass 2.11.3. Getting distribution for 'DateTime==2.12.0'. Got DateTime 2.12.0. Getting distribution for 'Acquisition==2.12.4'. Got Acquisition 2.12.4. Getting distribution for 'zope.app.testing==3.6.2'. Got zope.app.testing 3.6.2. Getting distribution for 'zope.app.appsetup==3.11'. Got zope.app.appsetup 3.11. Generated script '/home/mg/src/akl-website-z2.12-experiment/bin/runzope'. Generated script '/home/mg/src/akl-website-z2.12-experiment/bin/zopectl'. Generated interpreter '/home/mg/src/akl-website-z2.12-experiment/bin/py'. After that, it refuses to create a Data.fs and start up: mg@platonas:~/src/akl-website-z2.12-experiment $ bin/runzope Traceback (most recent call last): File "bin/runzope", line 93, in <module> Zope2.Startup.run.run() File "/home/mg/tmp/buildout-eggs/Zope2-2.12.2-py2.5-linux-i686.egg/Zope2/Startup/run.py", line 21, in run starter.prepare() File "/home/mg/tmp/buildout-eggs/Zope2-2.12.2-py2.5-linux-i686.egg/Zope2/Startup/__init__.py", line 87, in prepare self.startZope() File "/home/mg/tmp/buildout-eggs/Zope2-2.12.2-py2.5-linux-i686.egg/Zope2/Startup/__init__.py", line 264, in startZope Zope2.startup() File "/home/mg/tmp/buildout-eggs/Zope2-2.12.2-py2.5-linux-i686.egg/Zope2/__init__.py", line 47, in startup _startup() File "/home/mg/tmp/buildout-eggs/Zope2-2.12.2-py2.5-linux-i686.egg/Zope2/App/startup.py", line 72, in startup DB = dbtab.getDatabase('/', is_root=1) File "/home/mg/tmp/buildout-eggs/Zope2-2.12.2-py2.5-linux-i686.egg/Zope2/Startup/datatypes.py", line 283, in getDatabase name = self.getName(mount_path) File "/home/mg/tmp/buildout-eggs/Zope2-2.12.2-py2.5-linux-i686.egg/Zope2/Startup/datatypes.py", line 300, in getName self._mountPathError(mount_path) File "/home/mg/tmp/buildout-eggs/Zope2-2.12.2-py2.5-linux-i686.egg/Zope2/Startup/datatypes.py", line 273, in _mountPathError "No root database configured") ZConfig.ConfigurationError: No root database configured Huh? Result of that load_site.py error, or a missing manual step that I should have known to do despite it being not mentioned in the installation docs? I was brave enough to specify INSTANCEHOME as '.' in my zope.conf, because I strongly believe hardcoding absolute paths is dumb. mg@platonas:~/src/akl-website-z2.12-experiment $ cat etc/zope.conf %define INSTANCE . python $INSTANCE/bin/py instancehome $INSTANCE Cheers! Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development
2009/12/29 Marius Gedminas <marius@gedmin.as>:
I get the following error:
File "build/bdist.linux-i686/egg/Zope2/utilities/load_site.py", line 248 body = ("<html><head><title><dtml-var title_or_id></title> ^ SyntaxError: EOL while scanning single-quoted string
File "/home/mg/tmp/buildout-eggs/tmprWUwxL/Zope2-2.12.2-py2.5-linux-i686.egg/Zope2/utilities/load_site.py", line 248 body = ("<html><head><title><dtml-var title_or_id></title> ^ SyntaxError: EOL while scanning single-quoted string
I already fixed that error on the 2.12 branch. But it's a bogus message generated by setuptools. It tries to compile all scripts ending in .py when building the egg. The script in question is never used anywhere and is probably some bitrot.
After that, it refuses to create a Data.fs and start up:
File "/home/mg/tmp/buildout-eggs/Zope2-2.12.2-py2.5-linux-i686.egg/Zope2/Startup/datatypes.py", line 273, in _mountPathError "No root database configured") ZConfig.ConfigurationError: No root database configured
Huh? Result of that load_site.py error, or a missing manual step that I should have known to do despite it being not mentioned in the installation docs?
I was brave enough to specify INSTANCEHOME as '.' in my zope.conf, because I strongly believe hardcoding absolute paths is dumb.
mg@platonas:~/src/akl-website-z2.12-experiment $ cat etc/zope.conf %define INSTANCE .
python $INSTANCE/bin/py
instancehome $INSTANCE
Well. You didn't specify a database file in your zope,conf it seems. Without a declaration, there's no database. Hanno
On Tue, Dec 29, 2009 at 03:30:20PM +0100, Hanno Schlichting wrote:
2009/12/29 Marius Gedminas <marius@gedmin.as>:
I get the following error:
File "build/bdist.linux-i686/egg/Zope2/utilities/load_site.py", line 248 body = ("<html><head><title><dtml-var title_or_id></title> ^ SyntaxError: EOL while scanning single-quoted string
I already fixed that error on the 2.12 branch. But it's a bogus message generated by setuptools. It tries to compile all scripts ending in .py when building the egg. The script in question is never used anywhere and is probably some bitrot.
Ah, I thought it was something like this.
After that, it refuses to create a Data.fs and start up:
File "/home/mg/tmp/buildout-eggs/Zope2-2.12.2-py2.5-linux-i686.egg/Zope2/Startup/datatypes.py", line 273, in _mountPathError "No root database configured") ZConfig.ConfigurationError: No root database configured
Huh? Result of that load_site.py error, or a missing manual step that I should have known to do despite it being not mentioned in the installation docs?
I was brave enough to specify INSTANCEHOME as '.' in my zope.conf, because I strongly believe hardcoding absolute paths is dumb.
mg@platonas:~/src/akl-website-z2.12-experiment $ cat etc/zope.conf %define INSTANCE .
python $INSTANCE/bin/py
instancehome $INSTANCE
Well. You didn't specify a database file in your zope,conf it seems. Without a declaration, there's no database.
Makes sense, in a rather user-unfriendly way. May I suggest the documentation be amended to supply a closer-to-working zope.conf? I'm referring to this bit: http://docs.zope.org/zope2/releases/2.12/INSTALL.html#buildout-instances where I didn't notice the word "starting" in "Create a Zope configuration file starting as follows". Thanks for the very quick reply! Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development
Marius Gedminas wrote:
Well. You didn't specify a database file in your zope,conf it seems. Without a declaration, there's no database.
Makes sense, in a rather user-unfriendly way. May I suggest the documentation be amended to supply a closer-to-working zope.conf? I'm referring to this bit:
http://docs.zope.org/zope2/releases/2.12/INSTALL.html#buildout-instances
where I didn't notice the word "starting" in "Create a Zope configuration file starting as follows".
Hmm, well, a full zope.conf is a bit bloated to go in those docs, which is why I worded it the way I did... Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
On Tue, Dec 29, 2009 at 03:59:07PM +0000, Chris Withers wrote:
Marius Gedminas wrote:
Well. You didn't specify a database file in your zope,conf it seems. Without a declaration, there's no database.
Makes sense, in a rather user-unfriendly way. May I suggest the documentation be amended to supply a closer-to-working zope.conf? I'm referring to this bit:
http://docs.zope.org/zope2/releases/2.12/INSTALL.html#buildout-instances
where I didn't notice the word "starting" in "Create a Zope configuration file starting as follows".
Hmm, well, a full zope.conf is a bit bloated to go in those docs, which is why I worded it the way I did...
Is 46 lines too much? That's how much it takes to have python instancehome default-publisher-encoding # hm, what's this? first time I see one <eventlog> <logger access> <http-server> <zodb_db main> <zodb_db temporary> with a couple of %defines and comments. Or we could put a sample zope.conf somewhere on the web (heck, in svn is fine, using those nice *checkout* urls we've already used for downloading buildout's bootstrap.py or the Zope 2.12.2 versions.cfg). It'd be even better if there was a command I could run to generate an up-to-date default zope.conf, like mkzopeinstance does. Is there one? Maybe there's a place for "bin/zopectl init" that would mkdir etc var log and write a default etc/zope.conf? (Thanks to whoever came up with "bin/zopectl adduser", BTW, much appreciated!) Now the "using buildout" section of INSTALL.rst leaves the user to write one completely from scratch without any tool support or even a link to documentation, and I'd like to fix this in case I have to set up a Zope 2.x instance ever again ;-) Cheers! Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development
On Tue, Dec 29, 2009 at 9:43 PM, Marius Gedminas <marius@gedmin.as> wrote:
On Tue, Dec 29, 2009 at 03:59:07PM +0000, Chris Withers wrote:
Marius Gedminas wrote: It'd be even better if there was a command I could run to generate an up-to-date default zope.conf, like mkzopeinstance does. Is there one? Maybe there's a place for "bin/zopectl init" that would mkdir etc var log and write a default etc/zope.conf? (Thanks to whoever came up with "bin/zopectl adduser", BTW, much appreciated!)
Well, either you use mkzopeinstance, which indeed generates an instance for you with all things included, or if you use buildout you use a recipe like plone.recipe.zope2instance, in which case all it takes is: [instance] recipe = plone.recipe.zope2instance eggs = Zope2 user = admin:password http-address = 127.0.0.1:8080 and there's lots of documentation of the available options on the recipe page on PyPi. The current buildout docs are aimed at people who know how to set up Zope2 and don't want any help. Those are comfortable reading ZConfig definition files. Hanno
On Tue, Dec 29, 2009 at 09:56:01PM +0100, Hanno Schlichting wrote:
On Tue, Dec 29, 2009 at 9:43 PM, Marius Gedminas <marius@gedmin.as> wrote:
On Tue, Dec 29, 2009 at 03:59:07PM +0000, Chris Withers wrote:
Marius Gedminas wrote: It'd be even better if there was a command I could run to generate an up-to-date default zope.conf, like mkzopeinstance does. Is there one? Maybe there's a place for "bin/zopectl init" that would mkdir etc var log and write a default etc/zope.conf? (Thanks to whoever came up with "bin/zopectl adduser", BTW, much appreciated!)
Well, either you use mkzopeinstance, which indeed generates an instance for you with all things included,
*nod*
or if you use buildout you use a recipe like plone.recipe.zope2instance, in which case all it takes is:
[instance] recipe = plone.recipe.zope2instance eggs = Zope2 user = admin:password http-address = 127.0.0.1:8080
and there's lots of documentation of the available options on the recipe page on PyPi.
Ah, but then why The Official Zope 2.12 Installation Guide at http://docs.zope.org/zope2/releases/2.12/INSTALL.html#buildout-instances doesn't even mention plone.recipe.zope2instance? Should it? The namespace of the recipe alone is scary -- I don't want Plone, I just want Zope, cry bewildered newbie users!
The current buildout docs are aimed at people who know how to set up Zope2 and don't want any help. Those are comfortable reading ZConfig definition files.
Do you think that's how it should be, or would you like to improve the situation for Zope 2.13 (or even 2.12.3)? Do you think a command such as my suggested 'zopectl init' would be convenient for both new and advanced users? I'm willing to put some work to improve the docs or tools, but I need feedback! Cheers! Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development
On Tue, Dec 29, 2009 at 10:53 PM, Marius Gedminas <marius@gedmin.as> wrote:
Ah, but then why The Official Zope 2.12 Installation Guide at http://docs.zope.org/zope2/releases/2.12/INSTALL.html#buildout-instances doesn't even mention plone.recipe.zope2instance?
Should it? The namespace of the recipe alone is scary -- I don't want Plone, I just want Zope, cry bewildered newbie users!
Zope 2 has newbie users? I hope for them it has not :) To be honest the reason that recipe isn't mentioned there, is because Chris Withers worked on that section and didn't feel like it belongs there. And nobody else cared a great deal. Note that plone.recipe.zope2instance is actually in the collective, has a bug tracker on Launchpad and is licensed under the ZPL 2.1. The namespace plone just signals "written by the Plone community".
The current buildout docs are aimed at people who know how to set up Zope2 and don't want any help. Those are comfortable reading ZConfig definition files.
Do you think that's how it should be, or would you like to improve the situation for Zope 2.13 (or even 2.12.3)?
I actually don't care about that specific piece of documentation. There's hardly ever new users to Zope 2 that'd need it.
Do you think a command such as my suggested 'zopectl init' would be convenient for both new and advanced users?
zopectl init would be highly confusing. The "zopectl" script is usually associated with a particular Zope instance. That instance should have been created beforehand. But what would your tool do, that mkzopeinstance isn't doing? Hanno
On Tue, Dec 29, 2009 at 11:11:20PM +0100, Hanno Schlichting wrote:
On Tue, Dec 29, 2009 at 10:53 PM, Marius Gedminas <marius@gedmin.as> wrote:
Ah, but then why The Official Zope 2.12 Installation Guide at http://docs.zope.org/zope2/releases/2.12/INSTALL.html#buildout-instances doesn't even mention plone.recipe.zope2instance?
Should it? The namespace of the recipe alone is scary -- I don't want Plone, I just want Zope, cry bewildered newbie users!
Zope 2 has newbie users? I hope for them it has not :)
You got me here ;) I've only had to deal with Zope 2 when I helped random people/nonprofits upgrade/maintain their existing Zope 2 sites. (And by "helped" I mean "had to do that for them"). As for myself, I've used Zope 2 in the past (*many* years ago, so things like "how do you write a zope.conf from scratch" are flushed from my mental caches), before all this newfangled buildout stuff and so on, and I'd like to read docs to learn to use it.
To be honest the reason that recipe isn't mentioned there, is because Chris Withers worked on that section and didn't feel like it belongs there. And nobody else cared a great deal.
I care. What do y'all Zope-2-maintainer-people think about this patch? Index: doc/INSTALL.rst =================================================================== --- doc/INSTALL.rst (revision 107265) +++ doc/INSTALL.rst (working copy) @@ -136,11 +136,16 @@ command-line options, run the script wit Creating a buildout-based Zope Instance ======================================= -If you wish to use buildout to manage your Zope instance, then the +If you wish to use buildout to manage your Zope instance, there are recipes +like `plone.recipe.zope2instance`__ that automate everything. + + __ http://pypi.python.org/pypi/plone.recipe.zope2instance + +If you're a power user and want to drop to the basics, then the instance is created as follows: * Create a directory for your instance. In this directory, create a - ``etc``, ``logs`` and ``var`` subdirectories. + ``etc``, ``log`` and ``var`` subdirectories. * Download the following file into your instance directory: @@ -186,6 +191,8 @@ used. instancehome $INSTANCE + <rest of the stuff that goes into a zope.conf, e.g. databases and log files.> + .. highlight:: bash * Now, run the following commands::
Note that plone.recipe.zope2instance is actually in the collective, has a bug tracker on Launchpad and is licensed under the ZPL 2.1. The namespace plone just signals "written by the Plone community".
To those in the know, but let's not quibble.
The current buildout docs are aimed at people who know how to set up Zope2 and don't want any help. Those are comfortable reading ZConfig definition files.
Do you think that's how it should be, or would you like to improve the situation for Zope 2.13 (or even 2.12.3)?
I actually don't care about that specific piece of documentation. There's hardly ever new users to Zope 2 that'd need it.
I'll take that as a +0.
Do you think a command such as my suggested 'zopectl init' would be convenient for both new and advanced users?
zopectl init would be highly confusing. The "zopectl" script is usually associated with a particular Zope instance. That instance should have been created beforehand.
That's a good point.
But what would your tool do, that mkzopeinstance isn't doing?
Exist, for one. I don't have a bin/mkzopeinstance when I follow the instructions here: http://docs.zope.org/zope2/releases/2.12/INSTALL.html#buildout-instances Cheers! Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development
Marius Gedminas wrote:
What do y'all Zope-2-maintainer-people think about this patch?
Index: doc/INSTALL.rst =================================================================== --- doc/INSTALL.rst (revision 107265) +++ doc/INSTALL.rst (working copy) @@ -136,11 +136,16 @@ command-line options, run the script wit Creating a buildout-based Zope Instance =======================================
-If you wish to use buildout to manage your Zope instance, then the +If you wish to use buildout to manage your Zope instance, there are recipes +like `plone.recipe.zope2instance`__ that automate everything. + + __ http://pypi.python.org/pypi/plone.recipe.zope2instance + +If you're a power user and want to drop to the basics, then the instance is created as follows:
* Create a directory for your instance. In this directory, create a - ``etc``, ``logs`` and ``var`` subdirectories. + ``etc``, ``log`` and ``var`` subdirectories.
* Download the following file into your instance directory:
@@ -186,6 +191,8 @@ used.
instancehome $INSTANCE
+ <rest of the stuff that goes into a zope.conf, e.g. databases and log files.> + .. highlight:: bash
+ 0.5 from me.
Exist, for one. I don't have a bin/mkzopeinstance when I follow the instructions here: http://docs.zope.org/zope2/releases/2.12/INSTALL.html#buildout-instances
...that's because that gives you an instance, and if you have an instance you don't need mkzopeinstance ;-) mkzopeinstance is covered further up on that page, where a user who didn't know what buildout is would find it first :-P Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
Hanno Schlichting wrote:
To be honest the reason that recipe isn't mentioned there, is because Chris Withers worked on that section and didn't feel like it belongs there. And nobody else cared a great deal.
Exactly. That section is for people who are moving existing Zope instances to 2.12, and they already have zope.conf's...
Note that plone.recipe.zope2instance is actually in the collective, has a bug tracker on Launchpad and is licensed under the ZPL 2.1. The namespace plone just signals "written by the Plone community".
...run away! ;-)
Do you think that's how it should be, or would you like to improve the situation for Zope 2.13 (or even 2.12.3)?
I actually don't care about that specific piece of documentation. There's hardly ever new users to Zope 2 that'd need it.
Agreed. I certainly don't want to encourage new users to Zope 2.
Do you think a command such as my suggested 'zopectl init' would be convenient for both new and advanced users?
zopectl init would be highly confusing. The "zopectl" script is usually associated with a particular Zope instance. That instance should have been created beforehand.
Agreed. Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
Hanno Schlichting wrote:
Well, either you use mkzopeinstance, which indeed generates an instance for you with all things included, or if you use buildout you use a recipe like plone.recipe.zope2instance, in which case all it takes is:
[instance] recipe = plone.recipe.zope2instance eggs = Zope2 user = admin:password http-address = 127.0.0.1:8080
Yes, but this recipe is overly burdensome and unnecessary in its desire to spew out out. It's also obnoxious to have to manage your zope.conf through a limited set of config options to a recipe. I wish there was something like zc.zodbrecipes for Zope 2... ...especially if it used deployments.
The current buildout docs are aimed at people who know how to set up Zope2 and don't want any help. Those are comfortable reading ZConfig definition files.
...or the skeleton files that ship with the Zope 2 egg. cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
Marius Gedminas wrote:
Or we could put a sample zope.conf somewhere on the web (heck, in svn is fine, using those nice *checkout* urls we've already used for downloading buildout's bootstrap.py or the Zope 2.12.2 versions.cfg).
Sphinx also supports the ability to insert a link to a file. Maybe put the complete zope.conf as a link below the example start-of-zope.conf?
It'd be even better if there was a command I could run to generate an up-to-date default zope.conf, like mkzopeinstance does. Is there one?
In my dreams, I wanted a (waves hands something like) buildout recipe that would: - take a skeleton - zip it up - put that zipped data and some unpacking code into a single .py file For me, the skeleton would be a zope2 buildout instance containing: - bootstrap .py - a minimal buildout.cfg - some empty directories for logs, var, etc, etc Sadly, that instancebuilder script/recipe is likely to remain a dream :-(
Now the "using buildout" section of INSTALL.rst leaves the user to write one completely from scratch
Anyone using that section of the docs should be happy doing that ;-)
without any tool support or even a link to documentation, and I'd like to fix this in case I have to set up a Zope 2.x instance ever again ;-)
You know where the skeleton zope.conf lives though... Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
On Tue, Dec 29, 2009 at 10:50:23PM +0000, Chris Withers wrote:
Marius Gedminas wrote:
Now the "using buildout" section of INSTALL.rst leaves the user to write one completely from scratch
Anyone using that section of the docs should be happy doing that ;-)
without any tool support or even a link to documentation, and I'd like to fix this in case I have to set up a Zope 2.x instance ever again ;-)
You know where the skeleton zope.conf lives though...
Actually, no, I don't. (I took the zope.conf from the existing Zope 2.10 instance that I was migrating to 2.12.) Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development
participants (4)
-
Chris Withers -
Hanno Schlichting -
Marius Gedminas -
marius＠gedmin.as