[Zope3-Users] Zope3-users Digest, Vol 71, Issue 6

Discussion:

david ally

2010-10-22 09:01:40 UTC

Hi Marius,

Ok, does that mean zope2 will continue to exist as a separate project for as
long as possible?

David

Yes, there was a decision to rename Zope 3 to Bluebream. The reason is

that Zope 3 was never going to be a complete replacement for Zope 2,
carving out a different niche instead.

da> Secondly, I have been following the tutorial on bluebream
da> available at
da> http://bluebream.zope.org/doc/1.0/gettingstarted.html, but i got
da> stuck at this point ./bin/buildout with this error;

./bin/buildout

da> Develop: '/var/local/study/sampleproject/.'
da> install_dir

/var/local/study/sampleproject/develop-eggs/tmpvV1gjcbuild

da> Installing app.
da> Getting distribution for 'zope.security==3.7.3'.
da> install_dir /var/local/study/sampleproject/eggs/tmpUo9VBT
da> src/zope/security/_proxy.c:19: fatal error: Python.h: No such file or

directory
...

da> How do I resolve this ?

What OS? You need the equivalent of sudo apt-get install python-dev
for your distro.
Marius Gedminas
--
http://pov.lt/ -- Zope 3/BlueBream consulting and development
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
http://mail.zope.org/pipermail/zope3-users/attachments/20101021/daee1ee9/attachment-0001.bin
------------------------------
Message: 6
Date: Fri, 22 Oct 2010 00:36:55 +0200
Subject: Re: [Zope3-Users] z3c.form: small patch
Content-Type: text/plain; charset=UTF-8
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Marius,
thanks for the answer.

The bug tracker (launchpad) is a good place for patches, in theory.

Background: https://bugs.launchpad.net/singing-dancing/+bug/620608

which tracker at Launchpad? I've put the whole story into this bug
report, but the "home page" for z3c.form does not mention any
associated tracker, and neither does the z3c.form documentation page.

If you go to launchpad.net and search for z3c.form you will find the
project. In the project you will see the "Bugs" link at the top.
jens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAkzAwIcACgkQRAx5nvEhZLJVagCeIMKn21dZm51yh+gef3Oov63k
y68AoIzmTTX8lOkr+zh2oQqoJxWXyOb2
=iVAA
-----END PGP SIGNATURE-----
------------------------------
_______________________________________________
Zope3-users mailing list
https://mail.zope.org/mailman/listinfo/zope3-users
End of Zope3-users Digest, Vol 71, Issue 6
******************************************

david ally

2010-10-22 11:47:52 UTC

Permalink

Hi All,

Eventually, I was able to build the project, however, because of the speed
of my Internet link, it was constantly timing out, but fortunately, when i
restarted the build operation, it continued from where it stopped.

It got to a point where the build was still going but it gave this errors
and continued the build operation. Please find below;

Got zope.tal 3.5.2.
Getting distribution for 'RestrictedPython==3.6.0'.
SyntaxError: ('invalid syntax',
('build/bdist.linux-i686/egg/RestrictedPython/tests/before_and_after27.py',
30, 17, ' x = {y: y for y in whatever if y}\n'))

SyntaxError: ('invalid syntax',
('build/bdist.linux-i686/egg/RestrictedPython/tests/security_in_syntax27.py',
6, 13, ' {y: y for _restricted_name in x}\n'))

SyntaxError: ('invalid syntax',
('/home/david/sampleproject/eggs/tmpwTJ7tk/RestrictedPython-3.6.0-py2.6.egg/RestrictedPython/tests/before_and_after27.py',
30, 17, ' x = {y: y for y in whatever if y}\n'))

SyntaxError: ('invalid syntax',
('/home/david/sampleproject/eggs/tmpwTJ7tk/RestrictedPython-3.6.0-py2.6.egg/RestrictedPython/tests/security_in_syntax27.py',
6, 13, ' {y: y for _restricted_name in x}\n'))

Got RestrictedPython 3.6.0.
Getting distribution for 'zope.hookable==3.4.1'.
Got zope.hookable 3.4.1.
Getting distribution for 'zope.minmax==1.1.2'.
Got zope.minmax 1.1.2.

I finally got the sampleproject built successfully.

Thanks!

David

Post by david ally
Hi Marius,
Ok, does that mean zope2 will continue to exist as a separate project for
as long as possible?
David
Yes, there was a decision to rename Zope 3 to Bluebream. The reason is

that Zope 3 was never going to be a complete replacement for Zope 2,
carving out a different niche instead.

./bin/buildout

da> Develop: '/var/local/study/sampleproject/.'
da> install_dir

/var/local/study/sampleproject/develop-eggs/tmpvV1gjcbuild

or directory
...

da> How do I resolve this ?

Hi Marius,
thanks for the answer.

The bug tracker (launchpad) is a good place for patches, in theory.

Background: https://bugs.launchpad.net/singing-dancing/+bug/620608

which tracker at Launchpad? I've put the whole story into this bug
report, but the "home page" for z3c.form does not mention any
associated tracker, and neither does the z3c.form documentation page.

david ally

2010-10-22 12:09:16 UTC

Permalink

One more thing I can't login into the sample project welcome page at
http://localhost:8080, There was no place login credentials were require
during the creation and the build of the project.

Where do I get that info from?

David

Post by david ally
Hi All,
Eventually, I was able to build the project, however, because of the speed
of my Internet link, it was constantly timing out, but fortunately, when i
restarted the build operation, it continued from where it stopped.
It got to a point where the build was still going but it gave this errors
and continued the build operation. Please find below;
Got zope.tal 3.5.2.
Getting distribution for 'RestrictedPython==3.6.0'.
SyntaxError: ('invalid syntax',
('build/bdist.linux-i686/egg/RestrictedPython/tests/before_and_after27.py',
30, 17, ' x = {y: y for y in whatever if y}\n'))
SyntaxError: ('invalid syntax',
('build/bdist.linux-i686/egg/RestrictedPython/tests/security_in_syntax27.py',
6, 13, ' {y: y for _restricted_name in x}\n'))
SyntaxError: ('invalid syntax',
('/home/david/sampleproject/eggs/tmpwTJ7tk/RestrictedPython-3.6.0-py2.6.egg/RestrictedPython/tests/before_and_after27.py',
30, 17, ' x = {y: y for y in whatever if y}\n'))
SyntaxError: ('invalid syntax',
('/home/david/sampleproject/eggs/tmpwTJ7tk/RestrictedPython-3.6.0-py2.6.egg/RestrictedPython/tests/security_in_syntax27.py',
6, 13, ' {y: y for _restricted_name in x}\n'))
Got RestrictedPython 3.6.0.
Getting distribution for 'zope.hookable==3.4.1'.
Got zope.hookable 3.4.1.
Getting distribution for 'zope.minmax==1.1.2'.
Got zope.minmax 1.1.2.
I finally got the sampleproject built successfully.
Thanks!
David

that Zope 3 was never going to be a complete replacement for Zope 2,
carving out a different niche instead.

./bin/buildout

da> Develop: '/var/local/study/sampleproject/.'
da> install_dir

/var/local/study/sampleproject/develop-eggs/tmpvV1gjcbuild

or directory
...

da> How do I resolve this ?

Hi Marius,
thanks for the answer.
On Thu, 21.10.2010 at 19:03:27 +0300, Marius Gedminas <

The bug tracker (launchpad) is a good place for patches, in theory.

Background: https://bugs.launchpad.net/singing-dancing/+bug/620608

which tracker at Launchpad? I've put the whole story into this bug
report, but the "home page" for z3c.form does not mention any
associated tracker, and neither does the z3c.form documentation page.

david ally

2010-10-22 20:42:10 UTC

Permalink

Hi Zopeist,

Ok, I got the login credentials from the securitypolicy.zcml, documented for
newbies like myself, no assumptions!

David

Post by david ally
One more thing I can't login into the sample project welcome page at
http://localhost:8080, There was no place login credentials were require
during the creation and the build of the project.
Where do I get that info from?
David

that Zope 3 was never going to be a complete replacement for Zope 2,
carving out a different niche instead.

./bin/buildout

da> Develop: '/var/local/study/sampleproject/.'
da> install_dir

/var/local/study/sampleproject/develop-eggs/tmpvV1gjcbuild

or directory
...

da> How do I resolve this ?

Hi Marius,
thanks for the answer.
On Thu, 21.10.2010 at 19:03:27 +0300, Marius Gedminas <

The bug tracker (launchpad) is a good place for patches, in theory.

Background: https://bugs.launchpad.net/singing-dancing/+bug/620608

which tracker at Launchpad? I've put the whole story into this bug
report, but the "home page" for z3c.form does not mention any
associated tracker, and neither does the z3c.form documentation page.

Michael Howitz

2010-10-22 13:31:41 UTC

Permalink

Post by david ally
Hi All,
Eventually, I was able to build the project, however, because of the speed of my Internet link, it was constantly timing out, but fortunately, when i restarted the build operation, it continued from where it stopped.
It got to a point where the build was still going but it gave this errors and continued the build operation. Please find below;
Got zope.tal 3.5.2.
Getting distribution for 'RestrictedPython==3.6.0'.
SyntaxError: ('invalid syntax', ('build/bdist.linux-i686/egg/RestrictedPython/tests/before_and_after27.py', 30, 17, ' x = {y: y for y in whatever if y}\n'))
SyntaxError: ('invalid syntax', ('build/bdist.linux-i686/egg/RestrictedPython/tests/security_in_syntax27.py', 6, 13, ' {y: y for _restricted_name in x}\n'))
SyntaxError: ('invalid syntax', ('/home/david/sampleproject/eggs/tmpwTJ7tk/RestrictedPython-3.6.0-py2.6.egg/RestrictedPython/tests/before_and_after27.py', 30, 17, ' x = {y: y for y in whatever if y}\n'))
SyntaxError: ('invalid syntax', ('/home/david/sampleproject/eggs/tmpwTJ7tk/RestrictedPython-3.6.0-py2.6.egg/RestrictedPython/tests/security_in_syntax27.py', 6, 13, ' {y: y for _restricted_name in x}\n'))

These errors only occur because there are tests for Python 2.7 syntax constructs which are not yet exising in the Python 2.6 you used. You can safely ignore this errors.

Mit freundlichen Grüßen

--
Michael Howitz · ***@gocept.com · software developer
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1
Zope and Plone consulting and development

Toni Mueller

2010-10-23 12:27:19 UTC

Permalink

Hi David,

Post by david ally
Ok, does that mean zope2 will continue to exist as a separate project for as
long as possible?

I can't speak for anyone, but my superficial impression is that
still-required Zope2 features are being rebuilt using Zope3 technology
"under the hood", so normal users who either use a higher-level
framework, and/or who follow the Zope3 oriented documentation, will
only get small glimpses on the old Zope2 stuff.

Kind regards,
--Toni++