Post navigation

Return of the reposturgeon!

This is the repository editor I wrote about back in 2010; description here, architectural lessons here.

I did a conversion of the repo for the Roundup issue tracker, which had a messy history. It started out as CVS, got up-converted to Subversion, and I grabbed it with git-svn. Cleaning up the geological strata of conversion artifacts taught me some useful things.

Accordingly, a main feature in this release is a command that finds and removes zero-content commits created by cvs2svn->git-svn conversions. Also, the repository merge operation is no longer confused by out-of-order commits.

10 thoughts on “Return of the reposturgeon!”

Hmm, it seems reposurgeon is still fairly dependent on some deprecated Python 2.x syntax. Is there any plan to update it for Python 3 compatibility (it should not be hard with this program to maintain compatibility with both Python 2.6/2.7 and Python 3.x)?

> > Is there any plan to update [reposurgeon] for Python 3 compatibility
> Not urgently. I don’t think 2.x is going to go away for a while.

Certainly not for a long while. There are a LOT of popular tools that are written for Python 2.X that don’t need (or want) the hassles of converting to Python 3. Given that the most popular commercial Linux distro (Red Hat Enterprise Linux) only just shifted from Python 2.4 to Python 2.6 (and doesn’t include Python 3), you’ve basically got RedHat saying “Python 2.6 will be around for 5 more years, minimum”.

Someday you should remind me to tell you of my experiences as the lone Python programmer in the land of Perl. Suffice to say, it will be a cold day in Hell before I ever take up programming in Perl. Also, VirtualEnv is a life-saver for deploying complex Python applications. I get to control all of my dependencies in one place; the Perl programmers have chosen to depend upon CPAN, which is worse than dealing with the Devil.