[Grok-dev] How you can help improving Windows support
Roger Erens
roger.erens at e-s-c.biz
Tue Apr 14 03:52:28 EDT 2009
Hi Milind,
could you please report the results when you try:
I) look at the contents of E:\vgrok1\grok10a3\parts\etc\deploy.ini
and/or E:\vgrok1\grok10a3\parts\etc\debug.ini: are there hard coded
paths in it where \vgrok1 is replaced by \x0bgrok1 ?
II) you use the C:\ drive for installation instead of the E:\ drive
III) when you create a virtual environment with the --no-site-packages
option, I would expect an error about a missing win32api module or some
such. What happens when you invoke python after having activated your
virtual environment in step 7) and try to import win32api?
IV) after activating your virtual environment in step 7), issue the command:
echo %PATH%
You ought to find something like E:\vgrok\\Scripts in the output from
that command, meaning that easy_install and grokproject will be found
without prefixing them with \Scripts. If %PATH% does not contain that
directory _and_ you forgot to prefix the commands with \Scripts, you may
have used the system's easy_install and grokproject commands; you then
have a lot of cleaning up to do before retrying another installation
procedure!
Curious for the results of your experiments...
Roger
on 14-4-2009 2:44 Milind Khadilkar wrote:
> Hi,
> Thanks for your efforts. Despite your efforts, I have so far not been
> able to get grok10a3 working!
>
> 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:
> --------
> vgrok) E:\vgrok>Scripts\grokproject.exe grok10a3
> Enter user (Name of an initial administrator user): mk
> Enter passwd (Password for the initial administrator user):
> Downloading info about versions...
> Creating directory .\grok10a3
> Invoking zc.buildout...
> Develop: 'E:\\vgrok\\grok10a3\\.'
> Installing eggbasket.
> While:
> Installing.
> Getting section zpasswd.
> Initializing section zpasswd.
> Loading zc.buildout recipe entry z3c.recipe.dev:script.
>
> An internal error occured due to a bug in either zc.buildout or in a
> recipe being used:
> Traceback (most recent call last):
> File
> "c:\python24\lib\site-packages\zc.buildout-1.2.1-py2.4.egg\zc\buildout\bu
> ildout.py", line 1509, in main
> getattr(buildout, command)(args)
> File
> "c:\python24\lib\site-packages\zc.buildout-1.2.1-py2.4.egg\zc\buildout\bu
> ildout.py", line 357, in install
> [self[part]['recipe'] for part in install_parts]
> File
> "c:\python24\lib\site-packages\zc.buildout-1.2.1-py2.4.egg\zc\buildout\bu
> ildout.py", line 888, in __getitem__
> options._initialize()
> File
> "c:\python24\lib\site-packages\zc.buildout-1.2.1-py2.4.egg\zc\buildout\bu
> ildout.py", line 969, in _initialize
> recipe_class = _install_and_load(reqs, 'zc.buildout', entry, buildout)
> File
> "c:\python24\lib\site-packages\zc.buildout-1.2.1-py2.4.egg\zc\buildout\bu
> ildout.py", line 932, in _install_and_load
> return pkg_resources.load_entry_point(
> File
> "e:\vgrok\lib\site-packages\setuptools-0.6c9-py2.4.egg\pkg_resources.py",
> line 277, in load_entry_point
> return get_distribution(dist).load_entry_point(group, name)
> File
> "e:\vgrok\lib\site-packages\setuptools-0.6c9-py2.4.egg\pkg_resources.py",
> line 2180, in load_entry_point
> return ep.load()
> File
> "e:\vgrok\lib\site-packages\setuptools-0.6c9-py2.4.egg\pkg_resources.py",
> line 1913, in load
> entry = __import__(self.module_name, globals(),globals(), ['__name__'])
> File
> "c:\docume~1\mk\buildo~1\eggs\z3c.recipe.dev-0.5.4-py2.4.egg\z3c\recipe\d
> ev\script.py", line 23, in ?
> import ZConfig.schemaless
> ImportError: No module named schemaless
>
>
>
> 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:
> ----
> (vgrok1) E:\vgrok1\grok10a3>bin\paster.exe serve parts\etc\debug.ini
> Traceback (most recent call last):
> File "E:\vgrok1\grok10a3\bin\paster-script.py", line 124, in ?
> paste.script.command.run()
> File
> "C:\DOCUME~1\MK\BUILDO~1\eggs\pastescript-1.7.3-py2.4.egg\paste\script\co
> mmand.py", line 84, in run
> invoke(command, command_name, options, args[1:])
> File
> "C:\DOCUME~1\MK\BUILDO~1\eggs\pastescript-1.7.3-py2.4.egg\paste\script\co
> mmand.py", line 123, in invoke
> exit_code = runner.run(args)
> File
> "C:\DOCUME~1\MK\BUILDO~1\eggs\pastescript-1.7.3-py2.4.egg\paste\script\co
> mmand.py", line 218, in run
> result = self.command()
> File
> "C:\DOCUME~1\MK\BUILDO~1\eggs\pastescript-1.7.3-py2.4.egg\paste\script\se
> rve.py", line 271, in command
> self.logging_file_config(log_fn)
> File
> "C:\DOCUME~1\MK\BUILDO~1\eggs\pastescript-1.7.3-py2.4.egg\paste\script\co
> mmand.py", line 757, in logging_file_config
> fileConfig(config_file)
> File
> "C:\DOCUME~1\MK\BUILDO~1\eggs\pastescript-1.7.3-py2.4.egg\paste\script\ut
> il\logging_config.py", line 85, in fileConfig
> handlers = _install_handlers(cp, formatters)
> File
> "C:\DOCUME~1\MK\BUILDO~1\eggs\pastescript-1.7.3-py2.4.egg\paste\script\ut
> il\logging_config.py", line 158, in _install_handlers
> h = apply(klass, args)
> File "C:\Python24\lib\logging\__init__.py", line 757, in __init__
> stream = open(filename, mode)
> IOError: [Errno 2] No such file or directory:
> 'E:\x0bgrok1\\grok10a3/parts/log/access.log'
> ------
> 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!)
>
> Thanks again.
> Milind Khadilkar
>
> On Tue, Apr 14, 2009 at 3:54 AM, Roger Erens <roger.erens at e-s-c.biz
> <mailto:roger.erens at e-s-c.biz>> wrote:
>
> on 13-4-2009 16:58 Uli Fouquet wrote:
> > Hi there,
> >
> ...
>
> >
> > Good idea and many thanks for the port! You also added a large
> list of
> > TBD (to be discussed) topics, which might be of great value for
> our todo
> > list.
> >
> > I'd propose that we move this TBDs back to the wiki if you agree.
> This
> > way we could use the wiki as an easy to edit proto type for the
> install
> > howto while the text on grok.zope.org <http://grok.zope.org>
> represents our 'current state of
> > art' for installing Grok on Win platforms.
> >
> > Everytime a topic is 'finished' on the wiki, we then could port the
> > results back to the 'final' version on grok.zope.org
> <http://grok.zope.org>. So the wiki howto
> > would be our 'trunk' or development version (including comments,
> > proposals, TBDs, etc.) from which we generate 'releases' on
> > grok.zope.org <http://grok.zope.org>.
> >
>
> I cleaned up the HowTo and moved the procedure with the TBDs to the
> Wiki.
>
> ...
> >>>
> >>> http://wiki.zope.org/grok/WindowsSupportPlans
> >>>
> >>> where I added an extra section for that and/or file bug
> reports as
> >>> mentioned above. Of course you can also use the mailing list.
> >> Since I only have OEM-licensed Windows, I cannot start with a clean
> >> (virtualized) environment each time a grok/grokproject release
> is made.
> >> Therefore there may be some legacy settings stemming from
> actions that I
> >> forgot to mention.
> >
> > Unbelievable: one cannot start with a clean environment just
> because of
> > license? That's really bizarre, but will hit others too.
>
> Well, I actually meant that I don't have a separate MS Windows CD-Rom
> that I can use to install MS Windows into a virtual machine. So now I'm
> using my machine for daily use to test the installation procedure. When
> a new Grok release is made, I should uninstall my previous release.
> That's where the uncertainty about having legacy settings is creeping
> in. With a virtual machine and a separate MS Windows CD-Rom, one could
> be certain to start again with a clean environment.
>
> ...
> >
> > One first comment: you state in the howto that Python2.5 and 2.6
> are the
> > 'officially' supported versions. I think it is in fact Python2.4
> and 2.5
> > currently. Is that right?
>
> Yes, Ben made the same comment. I changed that.
>
> Roger
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org <mailto:Grok-dev at zope.org>
> http://mail.zope.org/mailman/listinfo/grok-dev
>
>
More information about the Grok-dev
mailing list