Re: [Zope-Checkins] SVN: Zope/branches/Zope-2_8-branch/ preparing 2.8.0 release for tomorrow
[Andreas Jung]
Log message for revision 30622: preparing 2.8.0 release for tomorrow
Andreas, which release will this be? If it's 2.8 final, I need to make a ZODB 3.4 to match it. According to http://www.zope.org/Wikis/DevSite/Projects/Zope2.8/MilestonePlan there wasn't another Zope 2.8 release scheduled until 2005/06/11, so I'm feeling a little lost here.
Hi, after resolving all outstanding problems with Zope 2.8 under Windows the next releases will be Zope 2.8 b2 (this weekend) and Zope 2.8.0 final (scheduled for 2005/06/11). I will cut a 2.8 release branch for Zope 2.8 b2. This means that the trunk is open for new development (Zope 2.9). Bugs (as always) have to be fixed on the 2.8 branch, SVN trunk and 2.7 branch (CVS). Andreas """ --On 3. Juni 2005 17:38:35 -0400 Tim Peters <tim.peters@gmail.com> wrote:
[Andreas Jung]
Log message for revision 30622: preparing 2.8.0 release for tomorrow
Andreas, which release will this be? If it's 2.8 final, I need to make a ZODB 3.4 to match it. According to
http://www.zope.org/Wikis/DevSite/Projects/Zope2.8/MilestonePlan
there wasn't another Zope 2.8 release scheduled until 2005/06/11, so I'm feeling a little lost here. _______________________________________________ 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 3. Juni 2005 17:38:35 -0400 Tim Peters <tim.peters@gmail.com> wrote:
[Andreas Jung]
Log message for revision 30622: preparing 2.8.0 release for tomorrow
Andreas, which release will this be? If it's 2.8 final, I need to make a ZODB 3.4 to match it. According to
http://www.zope.org/Wikis/DevSite/Projects/Zope2.8/MilestonePlan
there wasn't another Zope 2.8 release scheduled until 2005/06/11, so I'm feeling a little lost here.
Uppsss...my *big* mistake. Both the milestone plan and my iCAL calendar have an entry 2005/06/11 for 2.8 final but somehow I had in my mind I would release 2.8 final two weeks after b2 and not three weeks as planned :-/ So let's stick to the published schedule ...so everyone has one more week. Sorry for the confusion. me-becoming-older-and-more-braindead Andreas
[Andreas Jung]
... Uppsss...my *big* mistake. Both the milestone plan and my iCAL calendar have an entry 2005/06/11 for 2.8 final but somehow I had in my mind I would release 2.8 final two weeks after b2 and not three weeks as planned :-/ So let's stick to the published schedule ...so everyone has one more week. Sorry for the confusion.
Thanks, I like that better. I'll arrange to make and get ZODB 3.4 final into this over the coming week. Something still "needs to be done" about the Windows release process here. It looks like a Windows installer never got built for 2.8b2: http://www.zope.org/Products/Zope/2.8.0b2 Since Windows users never got to try 2.8b2, I'm not sure where the idea that the Windows problems have been fixed comes from (I realize some tests pass that used to fail on Windows -- users trying it is a much better "test case" <wink>). I'm trying to build a 2.8b2 installer now, and will upload it if/when that succeeds. First snag: the 2.8b2 tag was made with the WinBuilders part still pointing at Zope 2.8b1, so it wasn't possible to create a 2.8b2 Windows installer from the 2.8b2 tag. So that part of the release process also needs work. Does anyone believe that they're "in charge" of the Windows part of the Zope2 line? Someone identifiable needs to be; I can only volunteer time here because it's a weekend & I don't happen to have any urgent ZODB or ZRS bugs to stare at today. Later: Zope-2.8.0-b2-win32.exe is built now, and after some more testing I'll upload it to http://www.zope.org/Products/Zope/2.8.0b2 Windows users please give this a try -- it's your last (and in some sense, also your first <wink>) chance to try "the real" Zope 2.8 on Windows.
[Tim Peters]
... Later: Zope-2.8.0-b2-win32.exe is built now, and after some more testing I'll upload it to
http://www.zope.org/Products/Zope/2.8.0b2
Windows users please give this a try -- it's your last (and in some sense, also your first <wink>) chance to try "the real" Zope 2.8 on Windows.
I uploaded the installer there, but it doesn't work for me. This was built from svn://svn.zope.org/repos/main/Zope/tags/Zope-2-8-0-b2 after changing the Windows buildout in that tag to point at the correct 2.8b2 tarball. Then the build completed without error, and all the tests passed from the build/ directory ( bin\python bin\test.py -vv --all run from the inst/build/ directory, in a native DOS box, Win XP Pro SP2). These pieces went into it: C:\Code\28b2\inst>dir tmp ... 04/11/2005 02:52 PM 9,881,382 Python-2.3.5.exe 04/11/2005 02:52 PM 8,535,749 Python-2.3.5.tgz 04/18/2005 04:23 PM 3,940,871 pywin32-204.win32-py2.3.exe 06/04/2005 11:37 AM 5,298,645 Zope-2.8.0-b2.tgz ... Running the installer, and accepting all the defaults, appeared to work fine then. But the Zope service "doesn't work" -- "nothing visible happens", although it chews up a lot of CPU. The Windows Application log has lots of unencouraging entries then, like Zope_-1444516661 (Zope instance at C:\Zope-Instance): process terminated with exit code 1. Traceback (most recent call last): File "C:\Program Files\Zope-2.8.0-b2\lib\python\Zope2\Startup\run.py", line 56, in ? run() File "C:\Program Files\Zope-2.8.0-b2\lib\python\Zope2\Startup\run.py", line 21, in run starter.prepare() File "C:\Program Files\Zope-2.8.0-b2\lib\python\Zope2\Startup\__init__.py", line 99, in prepare self.registerSignals() File "C:\Program Files\Zope-2.8.0-b2\lib\python\Zope2\Startup\__init__.py", line 319, in registerSignals Signals.registerZopeSignals([self.cfg.eventlog, File "C:\Program Files\Zope-2.8.0-b2\lib\python\Signals\Signals.py", line 116, in registerZopeSignals SignalHandler.registerHandler(SIGTERM, shutdownFastHandler) File "C:\Program Files\Zope-2.8.0-b2\lib\python\Signals\WinSignalHandler.py", line 203, in registerHandler hevent = win32event.CreateEvent(sa, 0, 0, event_name) TypeError: The object is not a PySECURITY_ATTRIBUTES object then Zope_-1444516661 (Zope instance at C:\Zope-Instance): sleep 5 to avoid rapid restarts and then repeats of "created process" + PySECURITY_ATTRIBUTES + "sleep" with increasing times, and finally Zope_-1444516661 (Zope instance at C:\Zope-Instance): restarting too frequently; quit followed by The Zope_-1444516661 service has stopped (Zope instance at C:\Zope-Instance). Maybe that's unique to my box -- someone else want to try the installer? If it's not unique to my box, well, that isn't good <wink>. I don't have more time to look at this today. Mark, is the problem obvious to you? There's nothing particularly interesting in the instance's event.log; the tail end is just repetitions like this: 2005-06-04T12:45:26 INFO ZServer HTTP server started at Sat Jun 04 12:45:26 2005 Hostname: FATDESK Port: 8080 ------ 2005-06-04T12:46:09 INFO ZServer HTTP server started at Sat Jun 04 12:46:09 2005 Hostname: FATDESK Port: 8080 ------ 2005-06-04T12:47:32 INFO ZServer HTTP server started at Sat Jun 04 12:47:32 2005 Hostname: FATDESK Port: 8080 ------ 2005-06-04T12:50:16 INFO ZServer HTTP server started at Sat Jun 04 12:50:16 2005 Hostname: FATDESK Port: 8080
[Tim Peters, having trouble with 2.8b2 on Windows, ending with
Files\Zope-2.8.0-b2\lib\python\Signals\WinSignalHandler.py", line 203, in registerHandler hevent = win32event.CreateEvent(sa, 0, 0, event_name) TypeError: The object is not a PySECURITY_ATTRIBUTES object
] Just noting that someone else reported the same traceback, but against Zope 2.7.6 on Windows: http://www.zope.org/Collectors/Zope/1763 Same thing happens in 2.8b2 if I use runzope.bat from the instance (instead of trying to use the Windows service): C:\Zope-Instance\bin>runzope C:\Zope-Instance\bin>"C:\Program Files\Zope-2.8.0-b2\bin\python.exe" "C:\Program Files\Zope-2.8.0-b2\lib\python\Zope2\St artup\run.py" -C "C:\Zope-Instance\etc\zope.conf" Traceback (most recent call last): File "C:\Program Files\Zope-2.8.0-b2\lib\python\Zope2\Startup\run.py", line 56, in ? run() File "C:\Program Files\Zope-2.8.0-b2\lib\python\Zope2\Startup\run.py", line 21, in run starter.prepare() File "C:\Program Files\Zope-2.8.0-b2\lib\python\Zope2\Startup\__init__.py", line 99, in prepare self.registerSignals() File "C:\Program Files\Zope-2.8.0-b2\lib\python\Zope2\Startup\__init__.py", line 319, in registerSignals Signals.registerZopeSignals([self.cfg.eventlog, File "C:\Program Files\Zope-2.8.0-b2\lib\python\Signals\Signals.py", line 116, in registerZopeSignals SignalHandler.registerHandler(SIGTERM, shutdownFastHandler) File "C:\Program Files\Zope-2.8.0-b2\lib\python\Signals\WinSignalHandler.py", line 203, in registerHandler hevent = win32event.CreateEvent(sa, 0, 0, event_name) TypeError: The object is not a PySECURITY_ATTRIBUTES object
[Tim Peters, having trouble with 2.8b2 on Windows, ending with
Files\Zope-2.8.0-b2\lib\python\Signals\WinSignalHandler.py", line 203,
in registerHandler hevent = win32event.CreateEvent(sa, 0, 0, event_name) TypeError: The object is not a PySECURITY_ATTRIBUTES object
That sounds alot like duplicate copies of pywintypes23.dll have been loaded into the process, with the module 'pywintypes' being one instance explicitly loaded by Python, and the other being implicitly loaded by win32event.pyd etc dependencies. ... I've managed to reproduce this, and that does seem to be the problem. I think it will only happen when you have an existing pywintypes23.dll in your system32. A work-around is to ensure pywintypes is the first win32 module imported. I've attached a patch (SVN seems down at the moment) which seems to work for me. I'll try and come up with a decent fix for pywin32, but the patch should be fine to get this release out. [Actually, I'll just forward the patch to Tim. I've checked it in to 2.7.] Mark
There's a (another) new Zope-2.8.0-b2-win32.exe available for download at http://www.zope.org/Products/Zope/2.8.0b2/ and all Windows users are urged to try it. I don't know whether it will help with error popups if you happen to have an older (than build 204) version of pywin32/win32all installed, but it does repair the catastrophic problems with PySECURITY_ATTRIBUTES on my box. [Tim Peters, having trouble with 2.8b2 on Windows, ending with Files\Zope-2.8.0-b2\lib\python\Signals\WinSignalHandler.py", line 203, in registerHandler hevent = win32event.CreateEvent(sa, 0, 0, event_name) TypeError: The object is not a PySECURITY_ATTRIBUTES object ] [Mark Hammond]
That sounds alot like duplicate copies of pywintypes23.dll have been loaded into the process, with the module 'pywintypes' being one instance explicitly loaded by Python, and the other being implicitly loaded by win32event.pyd etc dependencies.
All obvious to the most casual observer <wink>.
... I've managed to reproduce this, and that does seem to be the problem. I think it will only happen when you have an existing pywintypes23.dll in your system32.
That was certainly the case on my box, as I have many Pythons installed independent of Zope/ZODB/ZRS, and installed pywin32 (build 204) for them too.
A work-around is to ensure pywintypes is the first win32 module imported. I've attached a patch (SVN seems down at the moment) which seems to work for me. I'll try and come up with a decent fix for pywin32, but the patch should be fine to get this release out.
[Actually, I'll just forward the patch to Tim. I've checked it in to 2.7.]
Thank you, Mark! I'll get it merged into Zope trunk, Zope 2.8 branch, and (although this is evil, I don't see a sane alternative -- checkins "should never" be made to a tag) the 2.8b2 tag. Andreas and Brian, Zope 2.7.6 is broken on Windows in the same way, as noted in the bug report I referenced yesterday: http://www.zope.org/Collectors/Zope/1763 IOW, a 2.7.7 release is needed, at least for Windows. If anyone pursues that, please let me know in advance so I can coordinate another ZODB 3.2 bugfix release to go along with it.
--On 5. Juni 2005 12:59:12 -0400 Tim Peters <tim.peters@gmail.com> wrote:
There's a (another) new Zope-2.8.0-b2-win32.exe available for download at
http://www.zope.org/Products/Zope/2.8.0b2/
and all Windows users are urged to try it. I don't know whether it will help with error popups if you happen to have an older (than build 204) version of pywin32/win32all installed, but it does repair the catastrophic problems with PySECURITY_ATTRIBUTES on my box.
"Run Zope in console" fails for me with "application has failed to start because pywintypes23.dll was not found..." -aj
--On 5. Juni 2005 19:14:52 +0200 Andreas Jung <lists@andreas-jung.com> wrote:
"Run Zope in console" fails for me with "application has failed to start because pywintypes23.dll was not found..."
After copying PyWintypes32.dll to $INSTANCE_HOME/bin I now get this PySECURITY_ATTRIBUTES error :-/ ....crap -aj
Andreas Jung wrote:
--On 5. Juni 2005 19:14:52 +0200 Andreas Jung <lists@andreas-jung.com> wrote:
"Run Zope in console" fails for me with "application has failed to start because pywintypes23.dll was not found..."
After copying PyWintypes32.dll to $INSTANCE_HOME/bin I now get this PySECURITY_ATTRIBUTES error :-/ ....crap
Must be yesterdays version then (i had just that error message, after removing an ancient pywintypes23.dll from C:\WINNT\system32). There are 2 pywintypes23.dlls now: $ZOPE_HOME\bin\PyWinTypes23.dll $ZOPE_HOME\bin\Lib\site-packages\pywin32_system32\pywintypes23.dll Zope starts fine now (although there are no messages in the console window anymore). Michael -- http://zope.org/Members/d2m http://planetzope.org
--On 5. Juni 2005 19:27:08 +0200 Michael Haubenwallner <michael@d2m.at> wrote:
There are 2 pywintypes23.dlls now: $ZOPE_HOME\bin\PyWinTypes23.dll $ZOPE_HOME\bin\Lib\site-packages\pywin32_system32\pywintypes23.dll
Zope starts fine now (although there are no messages in the console window anymore.
hmm...maybe Squid gave the old version :-/ trying to download it again. -aj
--On 5. Juni 2005 19:27:08 +0200 Michael Haubenwallner <michael@d2m.at> wrote:
Zope starts fine now (although there are no messages in the console window anymore).
hm...I retried again...with the same error? What is the md5sum of the .exe file? I have fb9...b798df6. -aj
[Michael Haubenwallner, to Andreas Jung]
Must be yesterdays version then (i had just that error message, after removing an ancient pywintypes23.dll from C:\WINNT\system32).
There are 2 pywintypes23.dlls now: $ZOPE_HOME\bin\PyWinTypes23.dll $ZOPE_HOME\bin\Lib\site-packages\pywin32_system32\pywintypes23.dll
Zope starts fine now (although there are no messages in the console window anymore).
Ya, I noticed that too. I don't know what's _intended_ here. The instance's event.log and Z2.log appear to be fine, and event.log in particular shows that you can shut down Zope cleanly now by hitting Ctrl+C in the DOS box from which you launched Zope; e.g., ... 2005-06-05T13:44:39 INFO ZServer HTTP server started at Sun Jun 05 13:44:39 2005 Hostname: FATDESK Port: 8080 ------ 2005-06-05T13:44:41 INFO Zope Ready to handle requests [... here I played with Zope for a brief time, then hit Ctrl+C ...] ------ 2005-06-05T13:46:01 INFO WinSignalHandler Caught signal SIGINT ------ 2005-06-05T13:46:01 INFO Z2 Shutting down ------ 2005-06-05T13:46:01 INFO ZServer closing HTTP to new connections
[Michael Haubenwallner, to Andreas Jung]
Must be yesterdays version then (i had just that error message, after removing an ancient pywintypes23.dll from C:\WINNT\system32).
There are 2 pywintypes23.dlls now: $ZOPE_HOME\bin\PyWinTypes23.dll $ZOPE_HOME\bin\Lib\site-packages\pywin32_system32\pywintypes23.dll
Zope starts fine now (although there are no messages in the console window anymore).
Ya, I noticed that too. I don't know what's _intended_ here.
The version in pywin32_system32 will never be used at runtime. It is a side-effect of the bdist_wininst hacks I pull in a normal pywin32 install. On my box, even with a version in %system32%, I now only ever get the Zope bin version loaded - which should mean people with older versions in system32 will not (since yesterdays patch) have a problem either. Note the careful use of 'should' <wink>' Mark
[Michael Haubenwallner, to Andreas Jung]
Must be yesterdays version then (i had just that error message, after removing an ancient pywintypes23.dll from C:\WINNT\system32).
There are 2 pywintypes23.dlls now: $ZOPE_HOME\bin\PyWinTypes23.dll $ZOPE_HOME\bin\Lib\site-packages\pywin32_system32\pywintypes23.dll
Zope starts fine now (although there are no messages in the console window anymore).
[Tim Peters]
Ya, I noticed that too. I don't know what's _intended_ here.
[Mark Hammond]
The version in pywin32_system32 will never be used at runtime. It is a side-effect of the bdist_wininst hacks I pull in a normal pywin32 install.
On my box, even with a version in %system32%, I now only ever get the Zope bin version loaded - which should mean people with older versions in system32 will not (since yesterdays patch) have a problem either. Note the careful use of 'should' <wink>'
My "that" above was ambiguous; I was actually talking about the lack of output in the console window, and I don't know what the intent is there. The "extra" DLLs in pywin32_system32 didn't bother me, but it's good to know too that they should not have <wink>. I've seen the 2.8b2 installer work fine on 3 other boxes since then, from Win2K to WinXP Pro, so I think this is in good shape for now. Thank you again for the help, Mark!
[Tim Peters]
There's a (another) new Zope-2.8.0-b2-win32.exe available for download at
http://www.zope.org/Products/Zope/2.8.0b2/
and all Windows users are urged to try it. I don't know whether it will help with error popups if you happen to have an older (than build 204) version of pywin32/win32all installed, but it does repair the catastrophic problems with PySECURITY_ATTRIBUTES on my box.
[Andreas Jung]
"Run Zope in console" fails for me with "application has failed to start because pywintypes23.dll was not found..."
Works for me (WinXP Pro SP2), although it's saner to open a DOS box, cd to your instance's bin/ directory, and type "runzope" there (I don't know why we install a "Run Zope in console" link -- I can't imagine that any serious user would start Zope that way, because the teensy DOS box it pops up simply vanishes if anything goes wrong). Please check the md5 on the installer you used, to make sure it's the _current_ installer. It should be $ md5sum Z* fb9aec9e3a0e5b3487752d5b7b798df6 *Zope-2.8.0-b2-win32.exe If that's not what you get, you have an older version.
--On 5. Juni 2005 13:43:39 -0400 Tim Peters <tim.peters@gmail.com> wrote:
[Tim Peters]
There's a (another) new Zope-2.8.0-b2-win32.exe available for download at
http://www.zope.org/Products/Zope/2.8.0b2/
and all Windows users are urged to try it. I don't know whether it will help with error popups if you happen to have an older (than build 204) version of pywin32/win32all installed, but it does repair the catastrophic problems with PySECURITY_ATTRIBUTES on my box.
[Andreas Jung]
"Run Zope in console" fails for me with "application has failed to start because pywintypes23.dll was not found..."
Works for me (WinXP Pro SP2), although it's saner to open a DOS box, cd to your instance's bin/ directory, and type "runzope" there (I don't know why we install a "Run Zope in console" link -- I can't imagine that any serious user would start Zope that way, because the teensy DOS box it pops up simply vanishes if anything goes wrong).
Same result...
Please check the md5 on the installer you used, to make sure it's the _current_ installer. It should be
$ md5sum Z* fb9aec9e3a0e5b3487752d5b7b798df6 *Zope-2.8.0-b2-win32.exe
That's what I have. My box (vmware) is pretty much a new XP installation with no old Python installation except a local Zope installation which its own Python (but not registered anywhere in the registry). -aj
[Tim Peters]
Please check the md5 on the installer you used, to make sure it's the _current_ installer. It should be
$ md5sum Z* fb9aec9e3a0e5b3487752d5b7b798df6 *Zope-2.8.0-b2-win32.exe
[Andreas Jung]
That's what I have. My box (vmware) is pretty much a new XP installation with no old Python installation except a local Zope installation which its own Python (but not registered anywhere in the registry).
I'm not sure what local Zope installation (LZI) means. Running a Windows Zope installer always writes registry keys, so if your LZI was created by running a Windows Zope installer, you do have stuff in the registry pointing at it. I don't know why that would matter, but maybe it does.
--On 5. Juni 2005 14:07:52 -0400 Tim Peters <tim.peters@gmail.com> wrote:
[Tim Peters]
Please check the md5 on the installer you used, to make sure it's the _current_ installer. It should be
$ md5sum Z* fb9aec9e3a0e5b3487752d5b7b798df6 *Zope-2.8.0-b2-win32.exe
[Andreas Jung]
That's what I have. My box (vmware) is pretty much a new XP installation with no old Python installation except a local Zope installation which its own Python (but not registered anywhere in the registry).
I'm not sure what local Zope installation (LZI) means. Running a Windows Zope installer always writes registry keys, so if your LZI was created by running a Windows Zope installer, you do have stuff in the registry pointing at it. I don't know why that would matter, but maybe it does.
So what would be the solution to get b2 running without touching this installation (which I need for my work)? Andreas
[Andreas Jung]
That's what I have. My box (vmware) is pretty much a new XP installation with no old Python installation except a local Zope installation which its own Python (but not registered anywhere in the registry).
[Tim Peters]
I'm not sure what local Zope installation (LZI) means. Running a Windows Zope installer always writes registry keys, so if your LZI was created by running a Windows Zope installer, you do have stuff in the registry pointing at it. I don't know why that would matter, but maybe it does.
[Andreas Jung]
So what would be the solution to get b2 running without touching this installation (which I need for my work)?
I don't know -- I'm still not even sure what LZI means to you. Resolution probably depends on some detail I wouldn't be able to guess, and I have no experience trying to run more than one installed Zope on a Windows box. Anyone else? Whatever LZI is, if it were my box I'd uninstall it, and reinstall it later (the uninstall process would leave its Zope instance home alone).
--On 5. Juni 2005 14:30:53 -0400 Tim Peters <tim.peters@gmail.com> wrote:
I don't know -- I'm still not even sure what LZI means to you. Resolution probably depends on some detail I wouldn't be able to guess, and I have no experience trying to run more than one installed Zope on a Windows box. Anyone else? Whatever LZI is, if it were my box I'd uninstall it, and reinstall it later (the uninstall process would leave its Zope instance home alone).
I have to check this by tomorrow. The application we are building embeds Zope somehow but I don't know about the details how this is done since I am not in charge for building process and the distribtuion (so I basically started the installer and did my development without having to care about window details)...but I'll do some investigations ... Andreas
Tim Peters wrote:
Works for me (WinXP Pro SP2), although it's saner to open a DOS box, cd to your instance's bin/ directory, and type "runzope" there (I don't know why we install a "Run Zope in console" link -- I can't imagine that any serious user would start Zope that way, because the teensy DOS box it pops up simply vanishes if anything goes wrong).
Sorry for the off-topic post but I could not help but raise a hand since I am someone who actually likes to run zope on my dev box this way. I just append "pause" to the end of the "runzope.bat" so the box stays open when something goes wrong. Perhaps this could be made default? A small but significant change, that would be, hrrrm? :-P Regards, Petri
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Petri Savolainen wrote:
Tim Peters wrote:
Works for me (WinXP Pro SP2), although it's saner to open a DOS box, cd to your instance's bin/ directory, and type "runzope" there (I don't know why we install a "Run Zope in console" link -- I can't imagine that any serious user would start Zope that way, because the teensy DOS box it pops up simply vanishes if anything goes wrong).
Sorry for the off-topic post but I could not help but raise a hand since I am someone who actually likes to run zope on my dev box this way.
I just append "pause" to the end of the "runzope.bat" so the box stays open when something goes wrong. Perhaps this could be made default? A small but significant change, that would be, hrrrm? :-P
A collector issue with a patch would be the best way to get such an improvement into the codebase: http://www.zope.org/Collectors/Zope Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCpD5F+gerLs4ltQ4RAmU6AKDEaigVYR2N5I9Tcn5qPRh15V4qcACg0FD/ aYy5NjSDCKkuCjvY3D02GbE= =wz4J -----END PGP SIGNATURE-----
"Run Zope in console" fails for me with "application has failed to start because pywintypes23.dll was not found..."
That is surprising :) The reason it *should* work is that pythonservice.exe, pythonw.exe and pywintypes23.dll are all in the same directory. One thing I ran into last night: I previously installed a Zope 2.8 build on my box and uninstalled it - however, the Instance Home for this installation was *not* manually removed. I then installed this b2 release - Zope itself was installed into a different directory, but the same Instance Home directory was used. As this Instance Home directory existed, Zope did *not* recreate certain key files in the Instance Home. Thus, zopeservice.py and runzope.bat pointed to the *old* Zope binary directory, not the new one. I could see how something like that could cause the problem. Mark
Tim Peters wrote:
Later: Zope-2.8.0-b2-win32.exe is built now, and after some more testing I'll upload it to
http://www.zope.org/Products/Zope/2.8.0b2
Windows users please give this a try -- it's your last (and in some sense, also your first <wink>) chance to try "the real" Zope 2.8 on Windows.
Just tried that on my Win2K Laptop - after starting "runzope.bat" is was presented with a windows alert box and no startup messages written to the command window. It took me some time to realize that Zope was already running. Login is possible and ZMI is working ok. Here is some data for you (especially the Alert-box content): http://www.zope.org/Members/d2m/zope-2.8.0-b2_windows/startup.txt http://www.zope.org/Members/d2m/zope-2.8.0-b2_windows/event.log The 'signal handler' problem seems to persist. Michael -- http://zope.org/Members/d2m http://planetzope.org
[Michael Haubenwallner, tries Zope-2.8.0-b2-win32.exe from http://www.zope.org/Products/Zope/2.8.0b2 ]
Just tried that on my Win2K Laptop - after starting "runzope.bat" is was presented with a windows alert box and no startup messages written to the command window. It took me some time to realize that Zope was already running. Login is possible and ZMI is working ok.
Here is some data for you (especially the Alert-box content): http://www.zope.org/Members/d2m/zope-2.8.0-b2_windows/startup.txt
The """ Windows Alert-Box (translated from German): ----------------- "?PyWinObject_AsDEVMODE@@YAHPAU_object@@PAPAU_devicemodeA@@H@Z" not found in DLL "pywintypes23.dll" """ there almost certainly means that Zope is picking up an unintended (old) version of pywin32 (also known as win32all, especially older versions). For example, if you have your own Python installation (apart from the one Zope ships with), and installed win32all for it, it appears hard to stop Zope's Python from finding that one instead of the pywin32 Zope ships with.
http://www.zope.org/Members/d2m/zope-2.8.0-b2_windows/event.log
The 'signal handler' problem seems to persist.
By this I think you mean these kinds of lines in your event.log: 2005-06-04T19:07:12 WARNING Z2 Can not install signal handlers. Please install (or upgrade) your pywin32 installation (https://sf.net/projects/pywin32) I believe that's also a consequence of Zope's Python picking up an unintended, old version of pywin32. The good (or maybe just ironic <wink>) news is that appears to allow Zope to at least start. If you uninstalled all older versions of pywin32/win32all, I bet you'd get the same result I got (Zope _would_ try to install signal handlers then, and Zope startup would die as a result). Thanks for trying it!
participants (6)
-
Andreas Jung -
Mark Hammond -
Michael Haubenwallner -
Petri Savolainen -
Tim Peters -
Tres Seaver