Grok should run on python 2.6

[Michael Haubenwallner-2]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Who is able to sketch the effort to make Grok available on Python 2.6  -
i remember it took me half a day to patch the eggs to run on Python 2.6
a year ago ( http://blog.d2m.at/2008/10/03/from-the-labs/ ).

Lets do it now and make it a Grok 1.1 release.

Regards
Michael

- --
http://blog.d2m.at
http://planetzope.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrxLdUACgkQl0uAvQJUKVaXeQCeMppM9+s1WWEm1miq9QzOlb+E
ay0AoKItxMek+zgh4fzXGhcI8RmYmee7
=Qiyw
-----END PGP SIGNATURE-----

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[Kevin Teague]

mmm, adding Python 2.6 support would be nice.

Here are the versions that I'm using to override the Grok 1.0 versions
to get Python 2.6 compatibility:

mechanize = 0.1.9
zope.app.appsetup = 3.8.0
zope.app.component = 3.5.0
zope.app.container = 3.6.1
zope.app.testing = 3.5.6
zope.testbrowser = 3.5.1
zope.session = 3.8.1

But AFAIK the Zope Toolkit is also Python 2.6 compatible, so when
that's ready (I haven't been following the status of the ZTK to
closely yet) migrating Grok to ZTK will also provide 2.6
compatibility.

It'd be nice to be able to do these migrations piecemeal, first do the
work to bump a Grok app to Python 2.6, then do the work to migrate the
app to ZTK 1.0. Well, obviously through the magic of Buildout it's
already easy to do this, but doing a Grok release which just bumps the
packages just enough to get to 2.6 would be good.
_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[Michael Haubenwallner-2]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kevin Teague wrote:

> mmm, adding Python 2.6 support would be nice.
>
> Here are the versions that I'm using to override the Grok 1.0 versions
> to get Python 2.6 compatibility:
>
> mechanize = 0.1.9
> zope.app.appsetup = 3.8.0
> zope.app.component = 3.5.0
> zope.app.container = 3.6.1
> zope.app.testing = 3.5.6
> zope.testbrowser = 3.5.1
> zope.session = 3.8.1
>
> But AFAIK the Zope Toolkit is also Python 2.6 compatible, so when
> that's ready (I haven't been following the status of the ZTK to
> closely yet) migrating Grok to ZTK will also provide 2.6
> compatibility.
>
> It'd be nice to be able to do these migrations piecemeal, first do the
> work to bump a Grok app to Python 2.6, then do the work to migrate the
> app to ZTK 1.0. Well, obviously through the magic of Buildout it's
> already easy to do this, but doing a Grok release which just bumps the
> packages just enough to get to 2.6 would be good.

Kevin, thank you for your information. I just needed to add the next
possible release of zope.app.form to your versions listing - there is no
more zope.app.component.back35 in zope.app.component3.5.0.
Here is my config to run with Python 2.6

[buildout]
extends = buildout.cfg

[versions]
mechanize = 0.1.9
zope.app.appsetup = 3.8.0
zope.app.component = 3.5.0
zope.app.container = 3.6.1
zope.app.form = 3.6.3
zope.app.testing = 3.5.6
zope.testbrowser = 3.5.1
zope.session = 3.8.1

This makes at least a Grok trunk checkout build, test and run under
Python 2.6.

Btw, i changed etc/site.zcml.in too, as the grok.View permission is not
existing anymore.

I wonder how these changes will work with existing projects though.

It would be nice to get some hints on how to migrate the trunk to ZTK 1.0

Regards
Michael

- --
http://blog.d2m.at
http://planetzope.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkryfPIACgkQl0uAvQJUKVaeuQCbBjlKD4J66D/1Uf/Fdy6wUQQp
2DQAoIihH0IxfWjj7zZy+tFI3Ml3ZH7e
=25Ij
-----END PGP SIGNATURE-----

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[Michael Haubenwallner-2]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kevin Teague wrote:
> It'd be nice to be able to do these migrations piecemeal, first do the
> work to bump a Grok app to Python 2.6, then do the work to migrate the
> app to ZTK 1.0. Well, obviously through the magic of Buildout it's
> already easy to do this, but doing a Grok release which just bumps the
> packages just enough to get to 2.6 would be good.

As i found out the ZTK 1.0 is a KGS. I changed Grok to include the ZTK
1.0 versions (this is changing 82 out of 113 package releases).

Buildout succeeded immediately. I had to change a single package
(grokcore.view) and 5 tests to make all tests run. The grokwiki sample
app starts and works. Python2.6 is supported too.

I am very surprised this worked at all and that easy.

I now need to test the setup against real applications written for Grok
1.0. Please let me know if there are any so far.

I proposed to make Grok 1.1 implement the changes
https://blueprints.launchpad.net/grok/+spec/ztk-support

Regards
Michael

- --
http://blog.d2m.at
http://planetzope.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkr1JdUACgkQl0uAvQJUKVa6UQCfekV4fJVVO/wEEsCxUVmfo/NP
AAIAoKbbFV16oiZhufK7M4DvmkBkr0bZ
=089K
-----END PGP SIGNATURE-----

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev