On Sep 29, Alexander Fischer <alexanderfisc...@ordnungsdienst.org> wrote:
> So, i am interested in 3.1 because 3.0 series is no more maintained. Makes sense. > 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 suppose this is the way to go. > I'll take a lot at the source at the weekend, If you're brave enough. :-) Not all the code is in a decent state, unfortunately. > I currently don't know all changed in detail. I can foresee some problems: - for some good reasons we defined our own __contains__, __getitem__ and has_key methods, in the imdb.utils._Container class, which more or less emulates a dictionary. If 2to3 replaces has_key calls with the 'x in d' syntax, we can face some problems (our has_key/__getitem__ and __contains__ methods work on different sets of data). - we heavily depend on third-party packages: BeautifulSoup (included in IMDbPY), lxml, SQLObject and/or SQLAlchemy. I fear that none of these is Python3-ready, but I may be wrong. - we have A LOT of voodoo-code in imdb.parser.sql.objectadapter, imdb.parser.sql.alchemyadapter and in the imdbpy2sql.py script, mostly for performance reasons. Anyway, a run of 2to3 is worth a try. Bye! -- Davide Alberani <davide.alber...@gmail.com> [GPG KeyID: 0x465BFD47] http://erlug.linux.it/~da/ ------------------------------------------------------------------------------ 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
