Re: [Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/ Repair invocation of Inno compiler -- it doesn't ( can't) work to
On Thu, Jan 26, 2006 at 07:57:44PM -0500, Tim Peters wrote: | Log message for revision 41456: | Repair invocation of Inno compiler -- it doesn't ( can't) work to | stick the path and /cc in the same quoted string. Unsure why that | change was made (it worked fine before -- and now). That change was so I can run: 'ISS_COMPILER=iscc.exe WinBuilders/buildout', because compile32.exe fires up the gui, and obviously that can't work with the buildbot. Obviously I just tested my command and not what worked before :( -- Sidnei da Silva Enfold Systems, LLC. http://enfoldsystems.com ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
RE: [Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/ Repair invocation of Inno compiler -- it doesn't ( can't) work to
[Tim Peters] Log message for revision 41456: Repair invocation of Inno compiler -- it doesn't ( can't) work to stick the path and /cc in the same quoted string. Unsure why that change was made (it worked fine before -- and now). [Sidnei da Silva] That change was so I can run: 'ISS_COMPILER=iscc.exe WinBuilders/buildout', because compile32.exe fires up the gui, and obviously that can't work with the buildbot. I don't see why not -- no interaction with the GUI is required, it simply pops up a window for as long as the Inno compiler runs. Then the window goes away again, all by itself. Obviously I just tested my command and not what worked before :( Let's leave it alone for tonight, then. You can do anything you want with all of it starting tomorrow ;-) ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/Zope-2_8-branch/ Collector #2013: improved XHTML conformance of error messages
Log message for revision 41457: Collector #2013: improved XHTML conformance of error messages o Some of the error messages did not close 'p' tags. Changed: U Zope/branches/Zope-2_8-branch/doc/CHANGES.txt U Zope/branches/Zope-2_8-branch/lib/python/ZPublisher/HTTPResponse.py -=- Modified: Zope/branches/Zope-2_8-branch/doc/CHANGES.txt === --- Zope/branches/Zope-2_8-branch/doc/CHANGES.txt 2006-01-27 00:57:44 UTC (rev 41456) +++ Zope/branches/Zope-2_8-branch/doc/CHANGES.txt 2006-01-27 01:31:00 UTC (rev 41457) @@ -27,6 +27,9 @@ Bugs Fixed + - Collector #2013: improved XHTML conformance of error messages, +some of which did not close 'p' tags. + - Collector #1999: fixed broken FTP rename functionality (RNFR now returns 350 as status code instead 250) Modified: Zope/branches/Zope-2_8-branch/lib/python/ZPublisher/HTTPResponse.py === --- Zope/branches/Zope-2_8-branch/lib/python/ZPublisher/HTTPResponse.py 2006-01-27 00:57:44 UTC (rev 41456) +++ Zope/branches/Zope-2_8-branch/lib/python/ZPublisher/HTTPResponse.py 2006-01-27 01:31:00 UTC (rev 41457) @@ -652,7 +652,7 @@ raise NotFound, self._error_html( Debugging Notice, Zope has encountered a problem publishing your object.p -\n%s % entry) +\n%s/p % entry) def badRequestError(self,name): self.setStatus(400) @@ -666,7 +666,7 @@ The parameter, em%s/em, % name + was omitted from the request.p + Make sure to specify all required parameters, + -and try the request again. +and try the request again./p ) def _unauthorized(self): @@ -679,9 +679,9 @@ m = strongYou are not authorized to access this resource./strong if self.debug_mode: if self._auth: -m = m + 'p\nUsername and password are not correct.' +m = m + 'p\nUsername and password are not correct./p' else: -m = m + 'p\nNo Authorization header found.' +m = m + 'p\nNo Authorization header found./p' raise Unauthorized, m def exception(self, fatal=0, info=None, @@ -771,7 +771,7 @@ if fatal and t is SystemExit and v.code == 0: body = self.setBody( (str(t), - 'Zope has exited normally.p' + self._traceback(t, v, tb)), + 'Zope has exited normally.p' + self._traceback(t, v, tb) + '/p'), is_error=1) else: try: @@ -782,7 +782,8 @@ body = self.setBody( (str(t), 'Sorry, a site error occurred.p' - + self._traceback(t, v, tb)), + + self._traceback(t, v, tb) + + '/p'), is_error=1) elif self.isHTML(b): # error is an HTML document, not just a snippet of html ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/tags/2.9.0/inst/WinBuilders/ Merge tim-2.9-windows-installer branch.
Log message for revision 41458: Merge tim-2.9-windows-installer branch. This is the code used to build the Zope 2.9.0 Windows installer. It bundles Python 2.4.2, lives in peace with zpkgtools, moves to InnoSetup 5, and simplifies most parts of the build-the- installer process. Changed: U Zope/tags/2.9.0/inst/WinBuilders/README.txt D Zope/tags/2.9.0/inst/WinBuilders/bin/makezope.bat A Zope/tags/2.9.0/inst/WinBuilders/bin/msvcr71.dll U Zope/tags/2.9.0/inst/WinBuilders/etc/zope.iss.in U Zope/tags/2.9.0/inst/WinBuilders/mk/common.mk U Zope/tags/2.9.0/inst/WinBuilders/mk/python.mk U Zope/tags/2.9.0/inst/WinBuilders/mk/zope.mk -=- Modified: Zope/tags/2.9.0/inst/WinBuilders/README.txt === --- Zope/tags/2.9.0/inst/WinBuilders/README.txt 2006-01-27 01:31:00 UTC (rev 41457) +++ Zope/tags/2.9.0/inst/WinBuilders/README.txt 2006-01-27 01:39:54 UTC (rev 41458) @@ -1,39 +1,63 @@ Quick instructions: -The buildout has been tested under Windows 2K and XP Pro SP2. It almost -works on Win98SE (see bottom of file for discussion). +The buildout has been tested under Windows 2K and XP Pro SP2. Setup Environment -- +Install Python 2.4.2 (or whatever is most current) by running its native +Windows installer from python.org. + +Note: Python 2.4 switched from using a Wise installer to using a +Microsoft .msi installer, and the latter is harder to work with. The +buildout used to extract Python source and binaries (.exe, .pyd, .dll) +from the Wise installer (which could be treated much like a zip file). +Now the Python installer isn't used at all. Instead, the Python +source is taken from the Python tarball release, and the binaries are +copied from your installed Python. + Install Cygwin from cygwin.org (the default installation should give you everything you need). -Install Microsoft Visual C++ 6.0 (or MSVC 7 once we get to Python 2.4) +Install Microsoft Visual C++ 7.1 (aka Visual Studio .NET 2003). This is +needed to compile Zope's Python C extensions compatible with Python 2.4 +(and 2.5, when that's released). -Install InnoSetup 4.2 from www.jrsofware.org (into its default location). -Versions earlier than 4.0.11 are known to not work; any 4.2.x release -or later should be fine. Inno 5.x versions do *not* work (it appears the -Inno custom dialog mechanism has changed in an incompatible way) +Install InnoSetup 5.1.5 (or later) from www.jrsoftware.org, into its +default location. Inno 4.x (or earlier) cannot work: Inno 5 introduced a +vastly simpler way to create the custom dialog pages we want. 'svn switch' to, or check out, the Zope tag for which an installer is to be -built. You want a native Windows checkout here, so that the text files have -Windows-appropriate line ends. +built. -Within a Zope checkout, parent directory of this package is inst. Make a -tmp directory, inst/tmp. Place the necessary pre-requisites in the tmp -directory. At the time of this writing, this includes: +Within a Zope checkout, the parent directory of this package is inst. Make +a tmp directory, inst/tmp. Place the necessary pre-requisites in the tmp +directory. At the time of this writing, these are: - - Python-2.3.5.tgz - - Python-2.3.5.exe (used for binary modules) - - pywin32-205.win32-py2.3.exe (extracts binaries and sources) - - Zope.tgz + - Python-2.4.2.tgz + - pywin32-205.win32-py2.4.exe + - Zope-2.9.0.tgz As time marches on, these version numbers will obviously change. See/edit mk/python.mk and mk/zope.mk for the exact versions required. +You also need to install the same Windows Python that Zope will repackage. +There doesn't appear to be a sane way to extract binaries (.exe, .pyd, +.dll, .lib) from an .msi installer, and building Python from source is a long + messy process on Windows. So python.mk just copies them from an installed +Python instead. Cautions: +- If you didn't accept the Python installer's default directory, or if + you did but it's on a different drive, you'll need to change + WIN_PYINSTALLEDDIR in python.mk. + +- The main Python DLL must live in WIN_PYINSTALLEDDIR too. Depending on + how you installed Python, that may be sitting in some Windows system + directory instead; if so, make a copy in the root of your Python + installation. + + Building @@ -85,21 +109,44 @@ Testing Zope -The test suite can be run from inst\build\: +XXX This doesn't work right starting with Zope 2.9: it's clumsier than it +XXX should be, and the functional tests don't even try to run (just the +XXX unit tests). +XXX Someone who understands how Zope3 testing from a zpkgtools-tarball build +XXX was made to work again may be able to help here. +The test suite can be run from inst\build\, after building the installer. + - Open a native (not Cygwin) DOS box. We want to test with the Python the - Zope
[Zope-Checkins] SVN: Zope/branches/2.9/ Collector #2013: improved XHTML conformance of error messages
Log message for revision 41459: Collector #2013: improved XHTML conformance of error messages o Some of the error messages did not close 'p' tags. Changed: U Zope/branches/2.9/doc/CHANGES.txt U Zope/branches/2.9/lib/python/ZPublisher/HTTPResponse.py -=- Modified: Zope/branches/2.9/doc/CHANGES.txt === --- Zope/branches/2.9/doc/CHANGES.txt 2006-01-27 01:39:54 UTC (rev 41458) +++ Zope/branches/2.9/doc/CHANGES.txt 2006-01-27 01:40:29 UTC (rev 41459) @@ -26,6 +26,9 @@ Bugs fixed + - Collector #2013: improved XHTML conformance of error messages, +some of which did not close 'p' tags. + - Collector #1999: fixed broken FTP rename functionality (RNFR now returns 350 as status code instead 250) Modified: Zope/branches/2.9/lib/python/ZPublisher/HTTPResponse.py === --- Zope/branches/2.9/lib/python/ZPublisher/HTTPResponse.py 2006-01-27 01:39:54 UTC (rev 41458) +++ Zope/branches/2.9/lib/python/ZPublisher/HTTPResponse.py 2006-01-27 01:40:29 UTC (rev 41459) @@ -664,7 +664,7 @@ raise NotFound, self._error_html( Debugging Notice, Zope has encountered a problem publishing your object.p -\n%s % entry) +\n%s/p % entry) def badRequestError(self,name): self.setStatus(400) @@ -678,7 +678,7 @@ The parameter, em%s/em, % name + was omitted from the request.p + Make sure to specify all required parameters, + -and try the request again. +and try the request again./p ) def _unauthorized(self): @@ -691,9 +691,9 @@ m = strongYou are not authorized to access this resource./strong if self.debug_mode: if self._auth: -m = m + 'p\nUsername and password are not correct.' +m = m + 'p\nUsername and password are not correct./p' else: -m = m + 'p\nNo Authorization header found.' +m = m + 'p\nNo Authorization header found./p' raise Unauthorized, m def exception(self, fatal=0, info=None, @@ -783,7 +783,7 @@ if fatal and t is SystemExit and v.code == 0: body = self.setBody( (str(t), - 'Zope has exited normally.p' + self._traceback(t, v, tb)), + 'Zope has exited normally.p' + self._traceback(t, v, tb) + '/p'), is_error=1) else: try: @@ -794,7 +794,8 @@ body = self.setBody( (str(t), 'Sorry, a site error occurred.p' - + self._traceback(t, v, tb)), + + self._traceback(t, v, tb) + + '/p'), is_error=1) elif self.isHTML(b): # error is an HTML document, not just a snippet of html ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.9/inst/WinBuilders/ Merge tim-2.9-windows-installer branch.
Log message for revision 41460: Merge tim-2.9-windows-installer branch. This is the code used to build the Zope 2.9.0 Windows installer. It bundles Python 2.4.2, lives in peace with zpkgtools, moves to InnoSetup 5, and simplifies most parts of the build-the- installer process. Changed: U Zope/branches/2.9/inst/WinBuilders/README.txt D Zope/branches/2.9/inst/WinBuilders/bin/makezope.bat A Zope/branches/2.9/inst/WinBuilders/bin/msvcr71.dll U Zope/branches/2.9/inst/WinBuilders/etc/zope.iss.in U Zope/branches/2.9/inst/WinBuilders/mk/common.mk U Zope/branches/2.9/inst/WinBuilders/mk/python.mk U Zope/branches/2.9/inst/WinBuilders/mk/zope.mk -=- Modified: Zope/branches/2.9/inst/WinBuilders/README.txt === --- Zope/branches/2.9/inst/WinBuilders/README.txt 2006-01-27 01:40:29 UTC (rev 41459) +++ Zope/branches/2.9/inst/WinBuilders/README.txt 2006-01-27 01:40:46 UTC (rev 41460) @@ -1,39 +1,63 @@ Quick instructions: -The buildout has been tested under Windows 2K and XP Pro SP2. It almost -works on Win98SE (see bottom of file for discussion). +The buildout has been tested under Windows 2K and XP Pro SP2. Setup Environment -- +Install Python 2.4.2 (or whatever is most current) by running its native +Windows installer from python.org. + +Note: Python 2.4 switched from using a Wise installer to using a +Microsoft .msi installer, and the latter is harder to work with. The +buildout used to extract Python source and binaries (.exe, .pyd, .dll) +from the Wise installer (which could be treated much like a zip file). +Now the Python installer isn't used at all. Instead, the Python +source is taken from the Python tarball release, and the binaries are +copied from your installed Python. + Install Cygwin from cygwin.org (the default installation should give you everything you need). -Install Microsoft Visual C++ 6.0 (or MSVC 7 once we get to Python 2.4) +Install Microsoft Visual C++ 7.1 (aka Visual Studio .NET 2003). This is +needed to compile Zope's Python C extensions compatible with Python 2.4 +(and 2.5, when that's released). -Install InnoSetup 4.2 from www.jrsofware.org (into its default location). -Versions earlier than 4.0.11 are known to not work; any 4.2.x release -or later should be fine. Inno 5.x versions do *not* work (it appears the -Inno custom dialog mechanism has changed in an incompatible way) +Install InnoSetup 5.1.5 (or later) from www.jrsoftware.org, into its +default location. Inno 4.x (or earlier) cannot work: Inno 5 introduced a +vastly simpler way to create the custom dialog pages we want. 'svn switch' to, or check out, the Zope tag for which an installer is to be -built. You want a native Windows checkout here, so that the text files have -Windows-appropriate line ends. +built. -Within a Zope checkout, parent directory of this package is inst. Make a -tmp directory, inst/tmp. Place the necessary pre-requisites in the tmp -directory. At the time of this writing, this includes: +Within a Zope checkout, the parent directory of this package is inst. Make +a tmp directory, inst/tmp. Place the necessary pre-requisites in the tmp +directory. At the time of this writing, these are: - - Python-2.3.5.tgz - - Python-2.3.5.exe (used for binary modules) - - pywin32-205.win32-py2.3.exe (extracts binaries and sources) - - Zope.tgz + - Python-2.4.2.tgz + - pywin32-205.win32-py2.4.exe + - Zope-2.9.0.tgz As time marches on, these version numbers will obviously change. See/edit mk/python.mk and mk/zope.mk for the exact versions required. +You also need to install the same Windows Python that Zope will repackage. +There doesn't appear to be a sane way to extract binaries (.exe, .pyd, +.dll, .lib) from an .msi installer, and building Python from source is a long + messy process on Windows. So python.mk just copies them from an installed +Python instead. Cautions: +- If you didn't accept the Python installer's default directory, or if + you did but it's on a different drive, you'll need to change + WIN_PYINSTALLEDDIR in python.mk. + +- The main Python DLL must live in WIN_PYINSTALLEDDIR too. Depending on + how you installed Python, that may be sitting in some Windows system + directory instead; if so, make a copy in the root of your Python + installation. + + Building @@ -85,21 +109,44 @@ Testing Zope -The test suite can be run from inst\build\: +XXX This doesn't work right starting with Zope 2.9: it's clumsier than it +XXX should be, and the functional tests don't even try to run (just the +XXX unit tests). +XXX Someone who understands how Zope3 testing from a zpkgtools-tarball build +XXX was made to work again may be able to help here. +The test suite can be run from inst\build\, after building the installer. + - Open a native (not Cygwin) DOS box. We want to
Re: [Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/ Repair invocation of Inno compiler -- it doesn't ( can't) work to
On Thu, Jan 26, 2006 at 08:30:40PM -0500, Tim Peters wrote: | [Tim Peters] | Log message for revision 41456: |Repair invocation of Inno compiler -- it doesn't ( can't) work to |stick the path and /cc in the same quoted string. Unsure why that |change was made (it worked fine before -- and now). | | [Sidnei da Silva] | That change was so I can run: 'ISS_COMPILER=iscc.exe | WinBuilders/buildout', because compile32.exe fires up the gui, and | obviously that can't work with the buildbot. | | I don't see why not -- no interaction with the GUI is required, it simply | pops up a window for as long as the Inno compiler runs. Then the window | goes away again, all by itself. I can surely say that it doesn't work with the buildbot. Maybe because it's running as a Windows Service. -- Sidnei da Silva Enfold Systems, LLC. http://enfoldsystems.com ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/ Collector #2013: improved XHTML conformance of error messages
Log message for revision 41461: Collector #2013: improved XHTML conformance of error messages o Some of the error messages did not close 'p' tags. Changed: U Zope/trunk/doc/CHANGES.txt U Zope/trunk/lib/python/ZPublisher/HTTPResponse.py -=- Modified: Zope/trunk/doc/CHANGES.txt === --- Zope/trunk/doc/CHANGES.txt 2006-01-27 01:40:46 UTC (rev 41460) +++ Zope/trunk/doc/CHANGES.txt 2006-01-27 01:47:38 UTC (rev 41461) @@ -197,6 +197,9 @@ Bugs Fixed + - Collector #2013: improved XHTML conformance of error messages, +some of which did not close 'p' tags. + - Collector #2002: fixed broken 'ls -R' functionality (didn't recurse properly subclasses of OFS.Folder) Modified: Zope/trunk/lib/python/ZPublisher/HTTPResponse.py === --- Zope/trunk/lib/python/ZPublisher/HTTPResponse.py2006-01-27 01:40:46 UTC (rev 41460) +++ Zope/trunk/lib/python/ZPublisher/HTTPResponse.py2006-01-27 01:47:38 UTC (rev 41461) @@ -679,7 +679,7 @@ raise NotFound, self._error_html( Debugging Notice, Zope has encountered a problem publishing your object.p -\n%s % entry) +\n%s/p % entry) def badRequestError(self,name): self.setStatus(400) @@ -693,7 +693,7 @@ The parameter, em%s/em, % name + was omitted from the request.p + Make sure to specify all required parameters, + -and try the request again. +and try the request again./p ) def _unauthorized(self): @@ -706,9 +706,9 @@ m = strongYou are not authorized to access this resource./strong if self.debug_mode: if self._auth: -m = m + 'p\nUsername and password are not correct.' +m = m + 'p\nUsername and password are not correct./p' else: -m = m + 'p\nNo Authorization header found.' +m = m + 'p\nNo Authorization header found./p' raise Unauthorized, m def exception(self, fatal=0, info=None, @@ -798,7 +798,7 @@ if fatal and t is SystemExit and v.code == 0: body = self.setBody( (str(t), - 'Zope has exited normally.p' + self._traceback(t, v, tb)), + 'Zope has exited normally.p' + self._traceback(t, v, tb) + '/p'), is_error=1) else: try: @@ -809,7 +809,8 @@ body = self.setBody( (str(t), 'Sorry, a site error occurred.p' - + self._traceback(t, v, tb)), + + self._traceback(t, v, tb) + + '/p'), is_error=1) elif self.isHTML(b): # error is an HTML document, not just a snippet of html ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
RE: [Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/ Repair invocation of Inno compiler -- it doesn't ( can't) work to
[Sidnei da Silva] I can surely say that it doesn't work with the buildbot. Maybe because it's running as a Windows Service. Well, that's a goofy idea -- nothing runs right as a service ;-) ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/inst/WinBuilders/ Merge tim-2.9-windows-installer branch.
Log message for revision 41462: Merge tim-2.9-windows-installer branch. This is the code used to build the Zope 2.9.0 Windows installer. It bundles Python 2.4.2, lives in peace with zpkgtools, moves to InnoSetup 5, and simplifies most parts of the build-the- installer process. Changed: U Zope/trunk/inst/WinBuilders/README.txt D Zope/trunk/inst/WinBuilders/bin/makezope.bat A Zope/trunk/inst/WinBuilders/bin/msvcr71.dll U Zope/trunk/inst/WinBuilders/etc/zope.iss.in U Zope/trunk/inst/WinBuilders/mk/common.mk U Zope/trunk/inst/WinBuilders/mk/python.mk U Zope/trunk/inst/WinBuilders/mk/zope.mk -=- Modified: Zope/trunk/inst/WinBuilders/README.txt === --- Zope/trunk/inst/WinBuilders/README.txt 2006-01-27 01:47:38 UTC (rev 41461) +++ Zope/trunk/inst/WinBuilders/README.txt 2006-01-27 01:52:31 UTC (rev 41462) @@ -1,39 +1,63 @@ Quick instructions: -The buildout has been tested under Windows 2K and XP Pro SP2. It almost -works on Win98SE (see bottom of file for discussion). +The buildout has been tested under Windows 2K and XP Pro SP2. Setup Environment -- +Install Python 2.4.2 (or whatever is most current) by running its native +Windows installer from python.org. + +Note: Python 2.4 switched from using a Wise installer to using a +Microsoft .msi installer, and the latter is harder to work with. The +buildout used to extract Python source and binaries (.exe, .pyd, .dll) +from the Wise installer (which could be treated much like a zip file). +Now the Python installer isn't used at all. Instead, the Python +source is taken from the Python tarball release, and the binaries are +copied from your installed Python. + Install Cygwin from cygwin.org (the default installation should give you everything you need). -Install Microsoft Visual C++ 6.0 (or MSVC 7 once we get to Python 2.4) +Install Microsoft Visual C++ 7.1 (aka Visual Studio .NET 2003). This is +needed to compile Zope's Python C extensions compatible with Python 2.4 +(and 2.5, when that's released). -Install InnoSetup 4.2 from www.jrsofware.org (into its default location). -Versions earlier than 4.0.11 are known to not work; any 4.2.x release -or later should be fine. Inno 5.x versions do *not* work (it appears the -Inno custom dialog mechanism has changed in an incompatible way) +Install InnoSetup 5.1.5 (or later) from www.jrsoftware.org, into its +default location. Inno 4.x (or earlier) cannot work: Inno 5 introduced a +vastly simpler way to create the custom dialog pages we want. 'svn switch' to, or check out, the Zope tag for which an installer is to be -built. You want a native Windows checkout here, so that the text files have -Windows-appropriate line ends. +built. -Within a Zope checkout, parent directory of this package is inst. Make a -tmp directory, inst/tmp. Place the necessary pre-requisites in the tmp -directory. At the time of this writing, this includes: +Within a Zope checkout, the parent directory of this package is inst. Make +a tmp directory, inst/tmp. Place the necessary pre-requisites in the tmp +directory. At the time of this writing, these are: - - Python-2.3.5.tgz - - Python-2.3.5.exe (used for binary modules) - - pywin32-205.win32-py2.3.exe (extracts binaries and sources) - - Zope.tgz + - Python-2.4.2.tgz + - pywin32-205.win32-py2.4.exe + - Zope-2.9.0.tgz As time marches on, these version numbers will obviously change. See/edit mk/python.mk and mk/zope.mk for the exact versions required. +You also need to install the same Windows Python that Zope will repackage. +There doesn't appear to be a sane way to extract binaries (.exe, .pyd, +.dll, .lib) from an .msi installer, and building Python from source is a long + messy process on Windows. So python.mk just copies them from an installed +Python instead. Cautions: +- If you didn't accept the Python installer's default directory, or if + you did but it's on a different drive, you'll need to change + WIN_PYINSTALLEDDIR in python.mk. + +- The main Python DLL must live in WIN_PYINSTALLEDDIR too. Depending on + how you installed Python, that may be sitting in some Windows system + directory instead; if so, make a copy in the root of your Python + installation. + + Building @@ -85,21 +109,44 @@ Testing Zope -The test suite can be run from inst\build\: +XXX This doesn't work right starting with Zope 2.9: it's clumsier than it +XXX should be, and the functional tests don't even try to run (just the +XXX unit tests). +XXX Someone who understands how Zope3 testing from a zpkgtools-tarball build +XXX was made to work again may be able to help here. +The test suite can be run from inst\build\, after building the installer. + - Open a native (not Cygwin) DOS box. We want to test with the Python the - Zope installer includes. -- cd to inst\build
[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/ This branch is no longer interesting -- it's been merged
Log message for revision 41463: This branch is no longer interesting -- it's been merged to Zope trunk, 2.9 branch, and 2.9.0 tag. Changed: D Zope/branches/tim-2.9-windows-installer/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-dev] Zope tests: 8 OK
Summary of messages to the zope-tests list. Period Wed Jan 25 12:01:01 2006 UTC to Thu Jan 26 12:01:01 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Wed Jan 25 21:03:17 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004098.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Wed Jan 25 21:04:47 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004099.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Wed Jan 25 21:06:17 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004100.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Jan 25 21:07:47 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004101.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Wed Jan 25 21:09:17 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004102.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Jan 25 21:10:48 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004103.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Jan 25 21:12:18 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004104.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Jan 25 21:13:48 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004105.html ___ 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] Zope definition on Wikipedia
I have made a little update on the Zope article on Wikipedia: http://en.wikipedia.org/wiki/Zope Here is the diff: http://en.wikipedia.org/w/index.php?title=Zopediff=36787848oldid=36094466 It would probably be very helpful if some knowledgeable people would also take some time to review the whole content of the article. Maybe split Zope 3 to a separate page, or at least start a page on the component architecture. A paragraph about Five would also be helpful. There are also some disputable assertions, like this one More recently the Zope community branched in two directions. The Plone community turned Zope into a nice-looking content management system, complete with modern well-designed style sheets. The original authors released Zope 3. that should be corrected. S. -- Stéfane Fermigier, Tel: +33 (0)6 63 04 12 77 (mobile). Nuxeo Collaborative Portal Server: http://www.nuxeo.com/cps Gestion de contenu web / portail collaboratif / groupware / open source! ___ 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] buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin6
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 zc-bbwin6. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 2909 Blamelist: anguenot,dobe,hdima,jim,oestermeier,rykomats,sidnei,tim_one,tseaver,yuppie BUILD FAILED: failed failed slave lost sincerely, -The Buildbot ___ 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 )
Re: [Zope] Re: Zope/Plone logon security strategy etc
Tino Wildenhain wrote: michael nt milne schrieb: Yes I agree, having checked on basic http authentication I need SSL. Basic http and cookie auth is insecure. I just feel that zope should have this facility even with a self signed certificate, so that you could do it without Apache and had more options. The option to even just have it on for site logon would be good. Yes you can do that. There are patches to use SSL directly w/ the ZServer. But usually its by far not worth the trouble. Apache or pound as frontend proxy are easy to setup and ease management and load balancing. _ Tino + 1 And heres a link to info re: ZopeSSL setup: http://www.zope.org/Members/Ioan/ZopeSSL I moved to Apache (for SSL) because its independent of Zope and it will give you SSL and the power of a world class server when you need it. ZopeSSL worked fine (when i last tried it, like zope 2.4x). David ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zope 2.8.x and python security audit
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello! I read on the german zope user group homepage, that Zope 2.8.4 is not supported on python 2.4.x, because of the missing security audit. That is good to know, but... who did the security audit for python 2.3.x? Where can I read about that? What was done? (Where is the protocol?) That is a nice argument why one should prefer plone/zope/python over typo3/php, but only if we can prove that... Can someone point me to more information about that topic? Regards, Sven Deichmann - -- - --- Information nimmt Gestalt an... - http://www.werkbank.com - --- Werkbank Multimedia GmbH * Bergstrasse 152 * 44791 Bochum * GER Fon: +49(0)234/ 935386-03 * Fax: 935386-06 * [EMAIL PROTECTED] - --- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkPYkr4ACgkQx3fK1szFYvn3TgCeLyI9ijZuj6lwG8Ijb8oxNgQ0 ce0Ani802ynidbjqe0IZN8CFQi/yUgP2 =XUY6 -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] [ANN] jsonserver for Z2 version 1.1.pre3 released [AJAX]
News in version 1.1.pre3 - bug fixes - more advanced Five support - base demos (quickstart) re-made with Five, besides the old five-less demos are available as well. - more advanced demos: the Click-to-edit-title example and a drag-and-drop shopping cart mini application. All done with plain Zope. General information --- Jsonserver provides an alternative way of AJAX client-server communication on Zope. Jsonserver enables Zope to act as a JSON-RPC server. JSON-RPC is an XML-RPC replacement. It is built on JSON, a javascript based data interchange format. JSON has bindings for more languages. On the client side, the jsolait javascript library contains both JSON and JSON-RPC support, besides other utilities. Characteristics of this approach are: - You can bind methods in javascript to Zope methods, python scripts or page templates and call them up directly from javascript in a synchronous or asynchronous way (RPC). - Both the call parameters and the return value can be strings, unicode strings, instances of any other builtin python data type, or structures built with the combination of tuples, lists and dicts. These get marshalled transparently with JSON. - As a consequence there is no necessity to use XML to pass around structured data, you can just structure your data with python and pass it directly (but of course you also have the possibility to pass around XML). - Passing of both positional and keyword parameters allows to call up page templates with request parameters. - Full client compatibility with the Zope3 version of jsonserver, i.e. the same client code will be able to run on Zope2 and Zope3 without a change. - Five supported. This version, 1.1.pre3 is a pre-release and considered to be beta. It can be installed on Zope 2.7 and 2.8 (for 2.7 you need to install Five). It is compatible with Plone and can be used from it without restrictions. (PLEASE READ release notes for how to fix a critical Plone bug.) More information, download, and installable demo product at http://www.zope.org/Members/ree/jsonserver2 . Please report bugs directly to me. -- Balazs Ree [EMAIL PROTECTED] ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Security class attribute
Now in Zope 2.9 I get these warnings::
2006-01-26 14:31:45 WARNING Init Class
Products.MyProduct.Homesite.FilesContainer has a security declaration
for nonexistent method 'FileManagement'
That's understandable because I've coded it like this::
class MyProduct(...):
security=ClassSecurityInfo()
security.declareProtected('View', 'FileManagement.html')
setattr(MyProduct, 'FileManagement.html', MyProduct.FileManagement)
In other words, I create methods after the class has been defined and
squeeze them in manually. Very convenient.
To avoid the WARNING message above I thought I could use
declareProtected() _after_ the the class has been defined just as with
the additional method; but no luck :(
I tried this::
class MyProduct(...):
security=ClassSecurityInfo()
setattr(MyProduct, 'FileManagement.html', MyProduct.FileManagement)
MyProduct.security.declareProtected('View', 'FileManagement.html')
But I'm getting::
AttributeError: type object 'MyProduct' has no attribute 'security'
Which I totally don't understand. To test my sanity I wrote this test
script which works fine::
class _Z:
def __init__(self):
self.z = Z
def declareProtected(self, *a,**k):
print ++declare something+
def foo():
print I'm being called
return _Z()
class A:
security=foo()
def __init__(self):
pass
A.security.declareProtected(foo)
print dir(A)
Which works like you'd expect with the followin output::
I'm being called
++declare something+
['__doc__', '__init__', '__module__', 'security']
What's going on [differently] in Zope? What am I missing?
--
Peter Bengtsson,
work www.fry-it.com
home www.peterbe.com
hobby www.issuetrackerproduct.com
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
RE: [Zope] Security class attribute
The ClassSecurityInfo is a convenience to provide a
halfway-sane spelling for a lot of ugliness under the
hood in setting up security.
IntializeClass (among other things) tells the CSI to
apply itself to the class to set everything up, then it
gets *removed* from the class.
I can't tell for sure from your code, but I suspect that
IntializeClass is being called on MyProduct *before* you
are doing your class augmentation -- if you can defer the
call until after you hack it, it should work.
If for some reason you can't defer the call to InitializeClass,
it should be safe to create another ClassSecurityInfo and apply
it manually, e.g.:
class MyProduct(...):
security=ClassSecurityInfo()
InitializeClass happens...
setattr(MyProduct, 'FileManagement.html', MyProduct.FileManagement)
xtra = ClassSecurityInfo()
xtra.security.declareProtected('View', 'FileManagement.html')
xtra.apply(MyProduct)
HTH,
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
Peter Bengtsson
Sent: Thursday, January 26, 2006 9:44 AM
To: [Zope]
Subject: [Zope] Security class attribute
Now in Zope 2.9 I get these warnings::
2006-01-26 14:31:45 WARNING Init Class
Products.MyProduct.Homesite.FilesContainer has a security declaration
for nonexistent method 'FileManagement'
That's understandable because I've coded it like this::
class MyProduct(...):
security=ClassSecurityInfo()
security.declareProtected('View', 'FileManagement.html')
setattr(MyProduct, 'FileManagement.html', MyProduct.FileManagement)
In other words, I create methods after the class has been defined and
squeeze them in manually. Very convenient.
To avoid the WARNING message above I thought I could use
declareProtected() _after_ the the class has been defined just as with
the additional method; but no luck :(
I tried this::
class MyProduct(...):
security=ClassSecurityInfo()
setattr(MyProduct, 'FileManagement.html', MyProduct.FileManagement)
MyProduct.security.declareProtected('View', 'FileManagement.html')
But I'm getting::
AttributeError: type object 'MyProduct' has no attribute 'security'
Which I totally don't understand. To test my sanity I wrote this test
script which works fine::
class _Z:
def __init__(self):
self.z = Z
def declareProtected(self, *a,**k):
print ++declare something+
def foo():
print I'm being called
return _Z()
class A:
security=foo()
def __init__(self):
pass
A.security.declareProtected(foo)
print dir(A)
Which works like you'd expect with the followin output::
I'm being called
++declare something+
['__doc__', '__init__', '__module__', 'security']
What's going on [differently] in Zope? What am I missing?
--
Peter Bengtsson,
work www.fry-it.com
home www.peterbe.com
hobby www.issuetrackerproduct.com
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
RE: [Zope] Can one nest macros with slots?
The situation: I have a main_template that does the looks of the site, with a main slot where the content goes, much like the standard templates give you. Now I have objects that behave similarly and share some interface components, so I figured I could try to create another macro, with another slot to fit inside that main slot, that all of the objects/content types could re-use. So I end up doing what I said below ... But that doesn't work :( I've come up with an alternative for now, though it's not as elegant as this I think ... But it'll have to do. If you care to keep reading, the details: main_template: define-macro=master ... some html ... define-slot=main / ... some html ... /define-macro shared template: use-macro=main_template/master fill-slot=main define-macro=shared ... some html ... define-slot=sharedslot / ... some html ... /define-macro /fill-slot /use-macro Object specific template: use-macro=shared fill-slot=sharedslot ... some html ... /fill-slot /use-macro This works without errors, except that only the first macro shared comes out, the master one never gets processed :( I would've expected this to be recursive ... Ah well :( Thanks! J.F. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of J Cameron Cooper Sent: January 26, 2006 12:52 AM To: Doyon, Jean-Francois Cc: zope@zope.org Subject: Re: [Zope] Can one nest macros with slots? Doyon, Jean-Francois wrote: I can't seem to do this: use-macro fill-slot define-macro ... Some html ... define-slot/define-slot ... Some html ... /define-macro /fill-slot /use-macro Allowing me to nest multiple reusable templates? I have objects with common interfaces which could easily share templates ... If I could do this! (The shared template still needs to endup in the master template). Or are there other techniques to achieve this? Macros are decided at compile time so that you can ask a template (which is not called) for its macros:: here/main_template/macros/master The code above would have macros being created in some other template at the time this macros is used, and I cannot imagine how they would be available. Why is a macro with whatever uses your common interfaces not suitable? You scenario is too vague for any other advice. --jcc -- Building Websites with Plone http://plonebook.packtpub.com/ ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Security class attribute
On 1/26/06, Brian Lloyd [EMAIL PROTECTED] wrote:
The ClassSecurityInfo is a convenience to provide a
halfway-sane spelling for a lot of ugliness under the
hood in setting up security.
IntializeClass (among other things) tells the CSI to
apply itself to the class to set everything up, then it
gets *removed* from the class.
I can't tell for sure from your code, but I suspect that
IntializeClass is being called on MyProduct *before* you
are doing your class augmentation -- if you can defer the
call until after you hack it, it should work.
No, I did the InitializeClass() *after* everything else.
So still no explaination. For what's going on.
If for some reason you can't defer the call to InitializeClass,
it should be safe to create another ClassSecurityInfo and apply
it manually, e.g.:
class MyProduct(...):
security=ClassSecurityInfo()
InitializeClass happens...
setattr(MyProduct, 'FileManagement.html', MyProduct.FileManagement)
xtra = ClassSecurityInfo()
xtra.security.declareProtected('View', 'FileManagement.html')
xtra.apply(MyProduct)
That's sort of what I've done now. My code looks something like this::
class MyProduct(...):
security = ClassSecurityInfo()
security.declareProtected('View','blabla')
def blabla():
pass
setattr(MyProduct, 'blabla.html', MyProduct.blabla)
security.declareProtected('View', 'blabla.html')
security.apply(MyProduct)
InitializeClass(MyProduct)
...and now everything seems to be happy.
Thanks for the advice.
HTH,
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
Peter Bengtsson
Sent: Thursday, January 26, 2006 9:44 AM
To: [Zope]
Subject: [Zope] Security class attribute
Now in Zope 2.9 I get these warnings::
2006-01-26 14:31:45 WARNING Init Class
Products.MyProduct.Homesite.FilesContainer has a security declaration
for nonexistent method 'FileManagement'
That's understandable because I've coded it like this::
class MyProduct(...):
security=ClassSecurityInfo()
security.declareProtected('View', 'FileManagement.html')
setattr(MyProduct, 'FileManagement.html', MyProduct.FileManagement)
In other words, I create methods after the class has been defined and
squeeze them in manually. Very convenient.
To avoid the WARNING message above I thought I could use
declareProtected() _after_ the the class has been defined just as with
the additional method; but no luck :(
I tried this::
class MyProduct(...):
security=ClassSecurityInfo()
setattr(MyProduct, 'FileManagement.html', MyProduct.FileManagement)
MyProduct.security.declareProtected('View', 'FileManagement.html')
But I'm getting::
AttributeError: type object 'MyProduct' has no attribute 'security'
Which I totally don't understand. To test my sanity I wrote this test
script which works fine::
class _Z:
def __init__(self):
self.z = Z
def declareProtected(self, *a,**k):
print ++declare something+
def foo():
print I'm being called
return _Z()
class A:
security=foo()
def __init__(self):
pass
A.security.declareProtected(foo)
print dir(A)
Which works like you'd expect with the followin output::
I'm being called
++declare something+
['__doc__', '__init__', '__module__', 'security']
What's going on [differently] in Zope? What am I missing?
--
Peter Bengtsson,
work www.fry-it.com
home www.peterbe.com
hobby www.issuetrackerproduct.com
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
--
Peter Bengtsson,
work www.fry-it.com
home www.peterbe.com
hobby www.issuetrackerproduct.com
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope - future planning
On 1/26/06, Jonathan [EMAIL PROTECTED] wrote: I have a fairly extensive application running on Zope 2.6 and would like to upgrade it for long-term maintainability. So I am looking for thoughts from the group as to whether it would be better to upgrade to the latest version of Zope 2, or 'bite-the-bullet' and upgrade to Zope 3. Only you can answer that question. Does anyone know the long term fate of Zope 2? (ie. is the plan to eventually move everything into Zope 3, then slowly fade Zope 2 from the picture, or will Zope 2 be with us forever?). No, Zope 2 is definitely destined to slowly fade, but that is a process that will take years, and should have no real impact on your decision now. The question now is how much work you think it will be to upgrade to 2.9, vs how much work you think it will be to rewrite the applictaion to 3.2. And that depends in turn very much on what kind of site you are running, what third-party products you are using and no on. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zope - future planning
I have a fairly extensive application running on Zope 2.6 and would like to upgrade it for long-term maintainability. So I am looking for thoughts from the group as to whether it would be better to upgrade to the latest version of Zope 2, or 'bite-the-bullet' and upgrade to Zope 3. Does anyone know the long term fate of Zope 2? (ie. is the plan to eventually move everything into Zope 3, then slowly fade Zope 2 from the picture, or will Zope 2 be with us forever?). Any and all thoughts gratefully appreciated! Thanks, Jonathan ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope - future planning
Lennart Regebro wrote: On 1/26/06, Jonathan [EMAIL PROTECTED] wrote: Does anyone know the long term fate of Zope 2? (ie. is the plan to eventually move everything into Zope 3, then slowly fade Zope 2 from the picture, or will Zope 2 be with us forever?). No, Zope 2 is definitely destined to slowly fade, but that is a process that will take years, and should have no real impact on your decision now. I'm not sure one should call it 'fade', but that's a debate about semantics. Right now, there's a lot of innovation going on in Zope 2 all the time. It's just that lots of that innovation is now shared with Zope 3 - Zope 2 and Zope 3 technologies are converging. This convergence will take many years to be complete. We probably aren't even clear yet exactly what complete means, as both Zope 2 and Zope 3 will continue to evolve. So, besides porting to Zope 3 directly, you could port your application not to Zope 3, but to a modern version of Zope 2, such as Zope 2.9, and use the Zope 3 technology in it (a large part of Zope 3 is included, and Five is there to make integration possible). It allows you to evolve your application more gradually. It also allows your application more easy portability to Zope 3 if you should need to later, as you're already using the technology. Zope 2 is open source, so as long as there are users interested in maintaining Zope 2, Zope 2 will be with us. There are *lots* of users of Zope 2, so there is no reason to worry about it for years to come. We do think Zope 2 will very slowly, step by step, turn more into a special application of Zope 3 technologies, and the framework bits that were important once in Zope 2 will be replaced gradually with bits from Zope 3. Regards, Martijn ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope - future planning
If it is fairly extensive I would think your best bet is to migrate up the 2.X ladder. 2.6 - 2.7.8 (shouldn't be too bumpy) 2.7.8 - 2.8.4 (ZCatalog issues) 2.8.4 - 2.9.x (lots of Zope 3 goodness) If you do those the jump into Zope 3 should be easier than not. I usually wait for a .3 or .4 release to get in. Jake ___ http://www.ZopeZone.com On Thu, January 26, 2006 11:11 am, Jonathan said: I have a fairly extensive application running on Zope 2.6 and would like to upgrade it for long-term maintainability. So I am looking for thoughts from the group as to whether it would be better to upgrade to the latest version of Zope 2, or 'bite-the-bullet' and upgrade to Zope 3. Does anyone know the long term fate of Zope 2? (ie. is the plan to eventually move everything into Zope 3, then slowly fade Zope 2 from the picture, or will Zope 2 be with us forever?). Any and all thoughts gratefully appreciated! Thanks, Jonathan ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.8.x and python security audit
--On 26. Januar 2006 10:13:35 +0100 Sven Deichmann [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello! I read on the german zope user group homepage, that Zope 2.8.4 is not supported on python 2.4.x, because of the missing security audit. That is good to know, but... who did the security audit for python 2.3.x? Where can I read about that? What was done? There was never an official protocol..the audit was executed at Zope Corporation (ask Jim Fulton for details). There were also some glitches with RestrictedPython that had to be fixed when switching to new Python version. (Where is the protocol?) That is a nice argument why one should prefer plone/zope/python over typo3/php, but only if we can prove that... I doubt that such an information matters much to _promote_ Zope Co. The weekly bugs in PHP are self-explanatory :-) -aj pgpQgRmjlwmQu.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope/Plone logon security strategy etc
michael nt milne wrote at 2006-1-25 18:55 +: Yeah I know the security aspects are good once you are in, however when you login it's possible for someone to grab your logon name and pass as it goes over the internet, as there's no encryption at all. Then obviously login themselves and compromise your sites. You might be interested in my DigestAuth product. It provides HTTP DigestAuthentication for Zope. Of course, HTTP authentication gives you less freedom than other forms of authentication (as the browser does the login). These other forms can be made safer by the use of https. -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Error importing objects 2.8 2.7
*Been working up some code on a zope 2.8.0 install, and I wanted to move it over to a live server. I keep getting this error: Error Type: AttributeError* *Error Value: 'module' object has no attribute '__newobj__' The new server is curious becuase it reads: * Zope Version (unreleased version, python 2.2.3, linux2) Python Version 2.2.3 (#1, Aug 8 2003, 08:44:02) [GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-13)] This was an RPM install as far as I remember. 2.7 I think Do I need to get 2.8.0 on this production box, or is there an easy fix to get this .zexp imported? thanks for any tips! -e- ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Error importing objects 2.8 2.7
On 1/27/06, Ed Colmar [EMAIL PROTECTED] wrote: *Been working up some code on a zope 2.8.0 install, and I wanted to moveit over to a live server.I keep getting this error: i've had problems moving stuff (zclass, .zexp) between 2.7 and 2.8 iirc, there were major changes between the two. your best bet would be upgrading your live server to 2.8 too hth-- http://myzope.kedai.com.my - my-zope org ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Error importing objects 2.8 2.7
--On 26. Januar 2006 14:55:40 -0800 Ed Colmar [EMAIL PROTECTED] wrote: *Been working up some code on a zope 2.8.0 install, and I wanted to move it over to a live server. I keep getting this error: Importing stuff from a new Zope version into an older Zope version was _never_ a supported feature. Only import between _identical_ versions. Anything else makes little sense and is unsupported. -aj pgpIiemndHdJY.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
