Py3k support

Bug #687601 reported by Stefano Rivera on 2010-12-08
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released

Bug Description

Py3k support would be nice :)

As a downstream user, I need all my dependencies to be py3k compatible before I can do anything serious about lp:ibid

Related branches

Marius Gedminas (mgedmin) wrote :

I'd love to have Python 3.x support, but I need a gentle push in the right direction to get me started. A patch would be best; a link to a package that already uses 2to3 to support both Pythons 2.x and 3.x might do. Especially if that package used doctests, which I've heard can cause problems for 2to3.

Changed in objgraph:
importance: Undecided → Wishlist
Stefano Rivera (stefanor) wrote :

I had a quick shot at it. After going down the 2to3 road (and trying to get test to work sanely) I realised that this module can be made to work in 2.x and 3.x without 2to3.

See my pure3k branch. I dropped support for 2.4 and 2.5, but those can be re-added with a small amount of glue (__func__, __self__, next()).

The test-suite produces different numbers of nodes, but I assume that's expected?

Alternatively, to go the 2to3 route, it may help to have the documentation in a subdirectory.

Marius Gedminas (mgedmin) wrote :

Since I only recently _added_ Python 2.4 support (after I got a patch from an actual user, debugging a memleak in an old Zope 2 instance), I'm unwilling to drop it.

I was already thinking about moving the docs to a subdirectory, since they're cluttering the root too much.

I'm not married to the 2to3 idea; if it's possible to have a single codebase without too much contortions, that's even better.

I'll take a closer look at your branch a bit later, when I have more time.


Marius Gedminas (mgedmin) wrote :

I don't know if you got an email notification about the merge proposal I created and commented on. If not, it's here:

Changed in objgraph:
status: New → Fix Committed
Changed in objgraph:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers