(Accidentally replied off list, sending to the list now) On 25 April 2012 12:27, Jerome Leclanche <[email protected]> wrote: > I've been working for a while now on a python implementation of xdg specs, > it works on both python2 and 3. PyXDG codebase is absolutely awful. Link > below if anyone's interested. It's not feature-complete yet though...
Thanks, Jerome. Do you have a feel for: - How long will it take to replace the functionality of PyXDG? - How similar will the interface be? Will adapting code that uses it just require renaming a few functions, or will it need other code to be refactored? I haven't got a particular interest in maintaining PyXDG myself, but there are quite a few other packages that depend on it. I think it would be pretty easy to make PyXDG Python 3 compatible, so I suggest we make a 0.20 release with just those changes, so that existing code can keep using it. Then we can encourage people to move to your interface over time. Vincent: > We can migrate the CVS repo to git, and give you access if you're interested > and nobody else steps up :-) Thanks, that sounds like a good idea. I'll start working out what changes are needed for Python 3. Thomas _______________________________________________ xdg mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xdg
