[Grok-dev] Grok 1.1 important issues

Souheil CHELFOUH trollfot at gmail.com
Sun Feb 21 12:59:18 EST 2010


Btw, test-ecosystem is failing heavily... I fixed some of the packages
already, but there lots of failing packages.

2010/2/20 Souheil CHELFOUH <trollfot at gmail.com>:
> This is a problem I'll correct
> It's a bug in the path formatting.
> I'll release 1.4.1 tomorrow without this problem.
>
> 2010/2/20 Steve Schmechel <steveschmechel at yahoo.com>:
>> I ran through your procedure with Ubuntu 9.10 and Python 2.6 and it worked perfectly.
>>
>> On Windows XP with Python 2.6, the initial buildout ends with the following error:
>>
>> <snip />
>>
>> Got megrok.layout 0.9.
>> Generated script 'C:\\vgrok\\trunk\\bin\\test-ecosystem-megrok.layout'.
>> Getting distribution for 'megrok.z3cform.tabular==0.2'.
>> Got megrok.z3cform.tabular 0.2.
>> Getting distribution for 'megrok.z3ctable==1.4.0'.
>> Traceback (most recent call last):
>>  File "<string>", line 1, in <module>
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 1712, in main
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 1700, in with_e
>> i_usage
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 1716, in <lambd
>> a>
>>  File "C:\Python26\Lib\distutils\core.py", line 152, in setup
>>    dist.run_commands()
>>  File "C:\Python26\Lib\distutils\dist.py", line 975, in run_commands
>>    self.run_command(cmd)
>>  File "C:\Python26\Lib\distutils\dist.py", line 995, in run_command
>>    cmd_obj.run()
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 211, in run
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 427, in easy_in
>> stall
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 476, in install
>> _item
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 655, in install
>> _eggs
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 930, in build_a
>> nd_install
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\easy_install.py", line 919, in run_set
>> up
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\sandbox.py", line 62, in run_setup
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\sandbox.py", line 105, in run
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\sandbox.py", line 64, in <lambda>
>>  File "setup.py", line 55, in <module>
>>  File "C:\Python26\Lib\distutils\core.py", line 152, in setup
>>    dist.run_commands()
>>  File "C:\Python26\Lib\distutils\dist.py", line 975, in run_commands
>>    self.run_command(cmd)
>>  File "C:\Python26\Lib\distutils\dist.py", line 995, in run_command
>>    cmd_obj.run()
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\bdist_egg.py", line 167, in run
>>  File "C:\Python26\Lib\distutils\cmd.py", line 333, in run_command
>>    self.distribution.run_command(command)
>>  File "C:\Python26\Lib\distutils\dist.py", line 995, in run_command
>>    cmd_obj.run()
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\egg_info.py", line 177, in run
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\egg_info.py", line 252, in find_source
>> s
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\egg_info.py", line 308, in run
>>  File "C:\vgrok\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\sdist.py", line 157, in read_template
>>  File "C:\Python26\Lib\distutils\command\sdist.py", line 336, in read_template
>>    self.filelist.process_template_line(line)
>>  File "C:\Python26\Lib\distutils\filelist.py", line 129, in process_template_line
>>    (action, patterns, dir, dir_pattern) = self._parse_template_line(line)
>>  File "C:\Python26\Lib\distutils\filelist.py", line 104, in _parse_template_line
>>    dir = convert_path(words[1])
>>  File "C:\Python26\Lib\distutils\util.py", line 191, in convert_path
>>    raise ValueError, "path '%s' cannot end with '/'" % pathname
>> ValueError: path 'docs/' cannot end with '/'
>> An error occured when trying to install megrok.z3ctable 1.4.0. Look above this message for any errors that were output by easy_install.
>> While:
>>  Installing test-ecosystem.
>>  Getting distribution for 'megrok.z3ctable==1.4.0'.
>> Error: Couldn't install: megrok.z3ctable 1.4.0
>>
>> (vgrok) C:\vgrok\trunk>
>>
>> <snip />
>>
>> I am installing into a virtual environment created with
>> "--no-site-packages" at the path shown above.
>>
>> Let me know if there are other things you want me to try.
>>
>> Steve
>>
>> --- On Fri, 2/19/10, Jan-Wijbrand Kolman <janwijbrand at gmail.com> wrote:
>>
>>> From: Jan-Wijbrand Kolman <janwijbrand at gmail.com>
>>> Subject: Re: [Grok-dev] Grok 1.1 important issues
>>> To: grok-dev at zope.org
>>> Date: Friday, February 19, 2010, 2:01 PM
>>> Hi Steve,
>>>
>>> Steve Schmechel <steveschmechel at yahoo.com>
>>> wrote:
>>> > I would like to help test this on Windows with Python
>>> 2.6, but I want
>>> > to be sure that my procedure is correct for what you
>>> intend to
>>> > determine.
>>> >
>>> > Could you please describe (or point to a document that
>>> describes) the
>>> > procedure for testing a potential Grok release?
>>>
>>> >
>>> > Are you testing the latest trunk code (checkout and
>>> run buildout), or
>>> > are you starting with grokproject and Grok version
>>> 1.1a2 and then
>>> > pulling in newer code?
>>> >
>>> > Are there any specific changes to the buildout.cfg or
>>> other
>>> > configuration files?
>>> >
>>> > How deep does the testing go?  Do we just run
>>> Grok-specific tests or
>>> > recurse into all the tests in the underlying packages
>>> and libraries?
>>> >
>>> > How many tests are expected to run and "pass"?
>>> >
>>> > I just want to be sure that if I say "the tests pass",
>>> we are talking
>>> > about the same tests.  (Assumptions are more
>>> dangerous if I do not
>>> > find a problem, because there will be no need for
>>> someone to further
>>> > investigate some specific finding.)
>>>
>>> Good questions. Let's see if I can answer them.
>>>
>>> In all cases I relied on the test coverage of the various
>>> packages
>>> involved.
>>>
>>> I did a checkout of the groktoolkit::
>>>
>>>   svn co http://svn.zope.org/repos/main/groktoolkit/trunk.
>>>
>>> With the python version I wanted to test with, I ran the
>>> bootstrap.py
>>> for the groktoolkit checkout. Then run ./bin/buildout. Then
>>> you can run
>>> the tests for grok and the grokcore.* family and martian -
>>> each in
>>> eachother's context::
>>>
>>>   ./bin/test-grok
>>>
>>> Since the groktoolkit points to the latest 1.1a2 release,
>>> you're not yet
>>> testing the grok trunk itself. To run all of these test
>>> against the grok
>>> trunk you can use the mr.developer extension script::
>>>
>>>   ./bin/develop activate grok$
>>>
>>> (Note the trailing "$". This is needed because the develop
>>> command will
>>> regard the name as a regex and without it, all packages
>>> with grok in
>>> their name are checked out).
>>>
>>> I then ran buildout again to have the script use this grok
>>> trunk
>>> checkout::
>>>
>>>   ./bin/buildout
>>>
>>> and ran the tests again::
>>>
>>>   ./bin/test-grok
>>>
>>> There should be no buildout errors nor test failures
>>> whatsoever.
>>>
>>>
>>> After that I reset the buildout::
>>>
>>>   ./bin/develop reset
>>>
>>>   ./bin/buildout
>>>
>>> The I removed the .installed.cfg, bin directory , parts
>>> directory and
>>> develop-eggs directory before re-running the bootstrap.py
>>> script with a
>>> different python version. Using a completely fresh
>>> groktoolkit checkout
>>> would work to of course.
>>>
>>> I hope this helps. I'm curious whether others would have
>>> any comments or
>>> suggestions to this approach.
>>>
>>> regards,
>>> jw
>>>
>>>
>>> _______________________________________________
>>> Grok-dev mailing list
>>> Grok-dev at zope.org
>>> https://mail.zope.org/mailman/listinfo/grok-dev
>>>
>>
>>
>>
>>
>> _______________________________________________
>> Grok-dev mailing list
>> Grok-dev at zope.org
>> https://mail.zope.org/mailman/listinfo/grok-dev
>>
>


More information about the Grok-dev mailing list