[Grok-dev] How do I add Python 2.6 support to Grok?

Alec Munro alecmunro at gmail.com
Wed Feb 18 23:19:07 EST 2009

No. We use a lot of ternary statements, and some of our other software
has bugs that are fixed by 2.6, but we can work around those if
necessary. I'll start testing with 2.5.

I'm principally annoyed that the version dependencies, and reasons
thereof, seem to be so difficult to address. As far as I can tell,4
out of my 5 problems could be solved very easily:
 - 325353: For requiring Visual C++ to build zope.security, isn't this
just a matter of someone providing a prebuilt binary to pypi?
 - 317081: Requiring ~\.buildout\default.cfg to use "Docume~1",
instead of "Documents and Settings". Seems like this should be an easy
fix, and I should hope is already fixed somewhere.
 - For the egg package version changes, these may already be in the trunk.
 - 315227: For the problem with temp dir removal, this may also be
fixed, according to a comment on the ticket.

The only one that seems troublesome is 324327, which actually seems to
be an incompatibility with Python2.6. But it doesn't affect any of my
code, because I don't use the web server.


On Wed, Feb 18, 2009 at 7:39 PM, Lennart Regebro <regebro at gmail.com> wrote:
> On Wed, Feb 18, 2009 at 21:19, Alec Munro <alecmunro at gmail.com> wrote:
>> Hi List,
>> As I have repeatedly mentioned, Grok doesn't work on Python 2.6, at
>> least on Windows. I've filed bugs, complained here in various threads,
>> yet there appears to be no progress, or even mockery of my
>> desperation.
>> The timing of this is getting to be increasingly critical, as I'm
>> weeks away from deploying this to 3 or 4 additional sites, and it's
>> going to leave a bad taste in everyone's mouth if they have to go
>> through what I did to get Grok installed.
>> I suppose it's my own naivete, expecting that I could start
>> development, and that the horribly broken installation process would
>> be fixed in the mean time.
> Well, yeah, Grok is based on Zope 3.4, which doesn't support 2.6
> officially, so there is no real concentrated effort to get Grok onto
> 2.6 just yet. Is there a reason you absolutely have to have 2.6?
> --
> Lennart Regebro: Pythonista, Barista, Notsotrista.
> http://regebro.wordpress.com/
> +33 661 58 14 64

More information about the Grok-dev mailing list