On May 08, Jesper Noehr <[EMAIL PROTECTED]> wrote: > Previously I suggested that there's a difference between doing the > same query over HTTP/1.0 and 1.1. I was wrong;
Yup, title2imdbID needs to be patched. There's a fixed version in the CVS (almost identical to your), and I've fixed also name2imdbID, even if there are very few names with a + sign... My local tests fails, and I've to investigate why, but I think it's just a minor issue. > Bottom line is: You can stay with urllib, but I highly recommend > switching to urllib2 anyway. The code for urllib2 is here; it must be tested, but if there aren't valid reasons to revert to urllib I think we'll stay with urllib2. Is it included in Python packages for mobiles? This is a thing that must be checked. > No point in using archaic modules in there. Are you sure that urllib is (about to be) considered obsolte? > I'm guessing this is due to the IMDbPyWeb account on imdb.com? A query with s=pt (s=pn for names) must return the movie page only if it is a _perfect_ "long imdb canonical title/name", otherwise it makes sense for the web server to return a list of title. The IMDbPyWeb is set to return directly the movie page if the query have just one "good enough" result; this is also the default, so there's no need to worry about users who access with adultSearch set to off. -- Davide Alberani <[EMAIL PROTECTED]> [PGP KeyID: 0x465BFD47] http://erlug.linux.it/~da/ ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Imdbpy-devel mailing list Imdbpy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
