Am 29.09.2009, 15:18 Uhr, schrieb Alexander Fischer <alexanderfisc...@ordnungsdienst.org>:
> Forwarded message from imdbpy-users to continue this thread in > imdby-devel > >> On Sep 28, Alexander Fischer <alexanderfisc...@o2online.de> wrote: >> >>> i am currently writing a plugin for an irc bot, but this bot is >>> written in python3. >> Woah! So ahead of the times! ;-) 3.0 or 3.1? >> >>> Will there be any support for python3 in the near/middle future? The >>> 2to3 script throws errors alot of errors :( >> Not so far, since I was always scared about the need to maintain >> two separated versions. >> Obviously it's my desire to support Python 3, and I'll look again >> at the output of 2to3 (I did some tests about a year ago - it was >> not THAT bad, if I remember correctly). >> If you want to help, you're welcomed. Basically I need an >> explanation of what it's required to port IMDbPY to Python 3 and - even >> more important - how the side-by-side development of the two >> branches will continue (dropping Python 2.X is out of question). >> This kind of discussions should take place in the imdbpy-devel >> mailing list; please subscribe if you want to help: >> http://lists.sourceforge.net/lists/listinfo/imdbpy-devel >> >>> p.s. imdbpy is pretty cool :) Used it for a kde plasmoid. >> Happy to hear it. :-) >> Can it be downloaded from somewhere? I'd like to add it to the >> list of IMDbPY-based programs. >> Bye! >> > > So, i am interested in 3.1 because 3.0 series is no more maintained. > > A possible solution for the problem with maintaining 2 versions (which > would really suck) of IMDbpy would be perhaps to bring the python2 > version > in a state, where the 2to3 script runs fine? I'll take a lot at the > source > at the weekend, if this way welcomed or you have a better suggestion. I > didn't do it because I hoped it is not required and your documentation is > excellent :) > > I currently don't know all changed in detail. Python3 is new to me, too, > but things should not be that problematic. > > http://docs.python.org/dev/3.0/whatsnew/3.0.html > http://docs.python.org/3.1/whatsnew/3.1.html > > The kde-plasmoid won't go to public because i am too lazy to maintain it, > but this is in my opinion essential part of the job. > > > cu Hello, Okay, i'm sorry to say, i wrote crap and i am sorry stealing your time. I think there were some rw-problems in my stabe version package. I currently checked out the svn and 2to3 worked like a charm with. u...@host[/home/user/imdbpy] for i in $( find trunk/ -name *.py ); do 2to3 -wn $i; done I copied it manually in the site-packagws folder and compiled the c file ./imdb/parser/sql/cutils.c by hand. I hope this is all, what setuptools do. There is no python3 version of setuptools yet. Now i get some errors, because strings are unicode already in python3 and decode-method is unknown. Need a deeper look at this, when i have more time. Thanks so far. cu ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Imdbpy-devel mailing list Imdbpy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
