Hi,<br>Thanks for your efforts. Despite your efforts, I have so far not been able to get grok10a3 working!<br><br>1. I believe --no-site-packages needs to be provided when using virtualenv. If I don't, I get the following error when using grokproject:<br>
--------<br>vgrok) E:\vgrok>Scripts\grokproject.exe grok10a3<br>Enter user (Name of an initial administrator user): mk<br>Enter passwd (Password for the initial administrator user):<br>Downloading info about versions...<br>
Creating directory .\grok10a3<br>Invoking zc.buildout...<br>Develop: 'E:\\vgrok\\grok10a3\\.'<br>Installing eggbasket.<br>While:<br> Installing.<br> Getting section zpasswd.<br> Initializing section zpasswd.<br>
Loading zc.buildout recipe entry z3c.recipe.dev:script.<br><br>An internal error occured due to a bug in either zc.buildout or in a<br>recipe being used:<br>Traceback (most recent call last):<br> File "c:\python24\lib\site-packages\zc.buildout-1.2.1-py2.4.egg\zc\buildout\bu<br>
ildout.py", line 1509, in main<br> getattr(buildout, command)(args)<br> File "c:\python24\lib\site-packages\zc.buildout-1.2.1-py2.4.egg\zc\buildout\bu<br>ildout.py", line 357, in install<br> [self[part]['recipe'] for part in install_parts]<br>
File "c:\python24\lib\site-packages\zc.buildout-1.2.1-py2.4.egg\zc\buildout\bu<br>ildout.py", line 888, in __getitem__<br> options._initialize()<br> File "c:\python24\lib\site-packages\zc.buildout-1.2.1-py2.4.egg\zc\buildout\bu<br>
ildout.py", line 969, in _initialize<br> recipe_class = _install_and_load(reqs, 'zc.buildout', entry, buildout)<br> File "c:\python24\lib\site-packages\zc.buildout-1.2.1-py2.4.egg\zc\buildout\bu<br>ildout.py", line 932, in _install_and_load<br>
return pkg_resources.load_entry_point(<br> File "e:\vgrok\lib\site-packages\setuptools-0.6c9-py2.4.egg\pkg_resources.py",<br> line 277, in load_entry_point<br> return get_distribution(dist).load_entry_point(group, name)<br>
File "e:\vgrok\lib\site-packages\setuptools-0.6c9-py2.4.egg\pkg_resources.py",<br> line 2180, in load_entry_point<br> return ep.load()<br> File "e:\vgrok\lib\site-packages\setuptools-0.6c9-py2.4.egg\pkg_resources.py",<br>
line 1913, in load<br> entry = __import__(self.module_name, globals(),globals(), ['__name__'])<br> File "c:\docume~1\mk\buildo~1\eggs\z3c.recipe.dev-0.5.4-py2.4.egg\z3c\recipe\d<br>ev\script.py", line 23, in ?<br>
import ZConfig.schemaless<br>ImportError: No module named schemaless<br><br><br><br>2. After recreating the virtual environment with the --no-site-packages switch, I manage to create the project, but when I try to run the server, I get the following error:<br>
----<br>(vgrok1) E:\vgrok1\grok10a3>bin\paster.exe serve parts\etc\debug.ini<br>Traceback (most recent call last):<br> File "E:\vgrok1\grok10a3\bin\paster-script.py", line 124, in ?<br> paste.script.command.run()<br>
File "C:\DOCUME~1\MK\BUILDO~1\eggs\pastescript-1.7.3-py2.4.egg\paste\script\co<br>mmand.py", line 84, in run<br> invoke(command, command_name, options, args[1:])<br> File "C:\DOCUME~1\MK\BUILDO~1\eggs\pastescript-1.7.3-py2.4.egg\paste\script\co<br>
mmand.py", line 123, in invoke<br> exit_code = runner.run(args)<br> File "C:\DOCUME~1\MK\BUILDO~1\eggs\pastescript-1.7.3-py2.4.egg\paste\script\co<br>mmand.py", line 218, in run<br> result = self.command()<br>
File "C:\DOCUME~1\MK\BUILDO~1\eggs\pastescript-1.7.3-py2.4.egg\paste\script\se<br>rve.py", line 271, in command<br> self.logging_file_config(log_fn)<br> File "C:\DOCUME~1\MK\BUILDO~1\eggs\pastescript-1.7.3-py2.4.egg\paste\script\co<br>
mmand.py", line 757, in logging_file_config<br> fileConfig(config_file)<br> File "C:\DOCUME~1\MK\BUILDO~1\eggs\pastescript-1.7.3-py2.4.egg\paste\script\ut<br>il\logging_config.py", line 85, in fileConfig<br>
handlers = _install_handlers(cp, formatters)<br> File "C:\DOCUME~1\MK\BUILDO~1\eggs\pastescript-1.7.3-py2.4.egg\paste\script\ut<br>il\logging_config.py", line 158, in _install_handlers<br> h = apply(klass, args)<br>
File "C:\Python24\lib\logging\__init__.py", line 757, in __init__<br> stream = open(filename, mode)<br>IOError: [Errno 2] No such file or directory: 'E:\x0bgrok1\\grok10a3/parts/log/access.log'<br>------<br>
3. Minor corrections: In steps 8 (easy_install grokproject) and 9 (grokproject <project_name>, the directory Scripts\ needs to be specified (unless by consensus it is understood!)<br><br>Thanks again.<br>Milind Khadilkar<br>
<br><div class="gmail_quote">On Tue, Apr 14, 2009 at 3:54 AM, Roger Erens <span dir="ltr"><<a href="mailto:roger.erens@e-s-c.biz">roger.erens@e-s-c.biz</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">on 13-4-2009 16:58 Uli Fouquet wrote:<br>
> Hi there,<br>
><br>
</div>...<br>
<div class="im"><br>
><br>
> Good idea and many thanks for the port! You also added a large list of<br>
> TBD (to be discussed) topics, which might be of great value for our todo<br>
> list.<br>
><br>
> I'd propose that we move this TBDs back to the wiki if you agree. This<br>
> way we could use the wiki as an easy to edit proto type for the install<br>
> howto while the text on <a href="http://grok.zope.org" target="_blank">grok.zope.org</a> represents our 'current state of<br>
> art' for installing Grok on Win platforms.<br>
><br>
> Everytime a topic is 'finished' on the wiki, we then could port the<br>
> results back to the 'final' version on <a href="http://grok.zope.org" target="_blank">grok.zope.org</a>. So the wiki howto<br>
> would be our 'trunk' or development version (including comments,<br>
> proposals, TBDs, etc.) from which we generate 'releases' on<br>
> <a href="http://grok.zope.org" target="_blank">grok.zope.org</a>.<br>
><br>
<br>
</div>I cleaned up the HowTo and moved the procedure with the TBDs to the Wiki.<br>
<br>
...<br>
<div class="im">>>><br>
>>> <a href="http://wiki.zope.org/grok/WindowsSupportPlans" target="_blank">http://wiki.zope.org/grok/WindowsSupportPlans</a><br>
>>><br>
>>> where I added an extra section for that and/or file bug reports as<br>
>>> mentioned above. Of course you can also use the mailing list.<br>
>> Since I only have OEM-licensed Windows, I cannot start with a clean<br>
>> (virtualized) environment each time a grok/grokproject release is made.<br>
>> Therefore there may be some legacy settings stemming from actions that I<br>
>> forgot to mention.<br>
><br>
> Unbelievable: one cannot start with a clean environment just because of<br>
> license? That's really bizarre, but will hit others too.<br>
<br>
</div>Well, I actually meant that I don't have a separate MS Windows CD-Rom<br>
that I can use to install MS Windows into a virtual machine. So now I'm<br>
using my machine for daily use to test the installation procedure. When<br>
a new Grok release is made, I should uninstall my previous release.<br>
That's where the uncertainty about having legacy settings is creeping<br>
in. With a virtual machine and a separate MS Windows CD-Rom, one could<br>
be certain to start again with a clean environment.<br>
<br>
...<br>
<div class="im">><br>
> One first comment: you state in the howto that Python2.5 and 2.6 are the<br>
> 'officially' supported versions. I think it is in fact Python2.4 and 2.5<br>
> currently. Is that right?<br>
<br>
</div>Yes, Ben made the same comment. I changed that.<br>
<div><div></div><div class="h5"><br>
Roger<br>
_______________________________________________<br>
Grok-dev mailing list<br>
<a href="mailto:Grok-dev@zope.org">Grok-dev@zope.org</a><br>
<a href="http://mail.zope.org/mailman/listinfo/grok-dev" target="_blank">http://mail.zope.org/mailman/listinfo/grok-dev</a><br>
</div></div></blockquote></div><br>