So I did a bit of work a little while ago to see what it would take to get
us running under Python 2.6 (note: just running, not using any of its new
features, but also not worrying about compatibility with 2.4).
With the exception of some of the dependency analysis tests, I have a
preliminary patch that lets us pass the testsuite.
http://cr.opensolaris.org/~dduvall/pkg-python26/
The unresolved issues are:
- The version of CherryPy we use doesn't support 2.6. I believe the next
micro version does, but I'm not sure how safe that is. So I added a
patch to munge our version to at least run under 2.6. I think
upgrading is probably safer, but wanted Shawn to weigh in.
- As part of the publication process, we use a module, xml.dom.ext.reader,
which is no longer available in 2.6 in Solaris. My hack solution was
to download and build pyxml as part of the process, but I think the
right answer is to use the built-in htmllib methods, if feasible.
Perhaps we should simply ask that the server not spit HTML back at us.
Either way, this is Shawn's code, and he should at least weigh in on
what the solution should be.
- The dependency analysis tests that fail are the python dependency
tests. The problem stems from telling it to analyze python files in
the filesystem, not ones in our workspace, or ones we create
specifically for the use of the tests. We look at a pkg(5) python file
in /usr/lib/python2.4/..., and it's got a shebang line indicating
python2.4, so the test expects that it'll be resolved with 2.4-based
files. But it gets resolved with 2.6-based files because we're running
in a 2.6 interpreter. I'm not sure how to solve that, but it points to
an underlying problem in the dependency analysis, in that it's not
going to be able to get the dependencies right for a python file
expecting an arbitrary interpreter version. We can simply move to the
2.6 regime analogous to what we have now, and just deal with the
intermediate failing tests, but I'd like to see the underlying problem
solved.
The rest should be fairly self-explanatory.
Thanks,
Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
