Re: [GsoC] your latest commit of tasks_udd.py
Hi Akshita,
On Thu, Jul 23, 2015 at 04:01:51PM +0530, Akshita Jha wrote:
>
> I had also downloaded the UDD dump yesterday. But, I am unable to reproduce
> this error. You had mentioned in one of your previous mails that
> index.de.html (german) is of size 0. But I do not find any index files of
> size 0 when I run ./tasks_udd debian-med nor are there any other files
> created which are of size 0.
> PFA the attached output of "$ ls -l index.* " in www/med/tasks_udd/ folder.
I'd love to simply forget this issue since Python 3 works perfectly. :-)
> > I'd happily test the Python 3 version. :-)
> >
>
> I have almost completed porting tasks_udd.py and blendstasktools_udd.py to
> Python 3 using 2to3 program. Apart from the obvious changes required in the
> scripts (which were done by the 2to3 tool mostly):
>
> 1) I had to make some changes to the .xhtml files present in template
> folder.
OK, seems just a replacement of has_key, right? Looks sensible.
> 2) Also, genshi seems to be broken for Python 3.4. The error I was getting :
>
> Exception: Unhandled node type <class '_ast.NameConstant'>
>
> was known [0] and I fixed it by applying all the patches for this specific
> error.
Ahh, you were able to fix this in the code? I understood[0] as if we
would need a fixed python3-genshi package. Could you please be a bit
more verbose about this? The thing is that we might need to backport
python2-genshi to Debian 8 to enable running our scripts on the final
destination. That's generally no problem but we need to remember this.
> 3) In addition to this, I needed to use set_client_encoding('utf-8') for
> psycopg2 as there was Encoding error in curs.fetchall(). This brings to my
> mind the question that while creating the database UDD, why can't we
> directly use encoding UTF-8 ? The reason seems to be that the encoding is
> SQL_ASCII since that is the format of export [1]. Won't it be beneficial if
> we encode using UTF-8 ?
This is what I always suggested and what was refused by the main UDD
developers. I admit I do not remmeber their reasons nor whether I have
understood them when they issued them. I think for the moment we should
take the SQL_ASCII as a given nuisance we can hopefully work around
(while I agree with you that UTF-8 would be beneficial.
The right mailing list to discuss UDD issues is
debian-qa@lists.debian.org.
Kind regards
Andreas.
> [0] http://genshi.edgewall.org/ticket/582
> [1] https://wiki.debian.org/UltimateDebianDatabase/Hacking
> -rw-rw-r-- 1 akshita akshita 15656 Jul 23 15:21 index.cs.html
> -rw-rw-r-- 1 akshita akshita 16368 Jul 23 15:21 index.da.html
> -rw-rw-r-- 1 akshita akshita 16445 Jul 23 15:21 index.de.html
> -rw-rw-r-- 1 akshita akshita 15657 Jul 23 15:21 index.en.html
> -rw-rw-r-- 1 akshita akshita 15704 Jul 23 15:21 index.es.html
> -rw-rw-r-- 1 akshita akshita 15703 Jul 23 15:21 index.fi.html
> -rw-rw-r-- 1 akshita akshita 16853 Jul 23 15:21 index.fr.html
> -rw-rw-r-- 1 akshita akshita 15656 Jul 23 15:22 index.hu.html
> -rw-rw-r-- 1 akshita akshita 16259 Jul 23 15:22 index.it.html
> -rw-rw-r-- 1 akshita akshita 17324 Jul 23 15:22 index.ja.html
> -rw-rw-r-- 1 akshita akshita 15627 Jul 23 15:22 index.ko.html
> -rw-rw-r-- 1 akshita akshita 15656 Jul 23 15:22 index.nl.html
> -rw-rw-r-- 1 akshita akshita 16383 Jul 23 15:22 index.pl.html
> -rw-rw-r-- 1 akshita akshita 16304 Jul 23 15:22 index.pt.html
> -rw-rw-r-- 1 akshita akshita 22249 Jul 23 15:22 index.ru.html
> -rw-rw-r-- 1 akshita akshita 15653 Jul 23 15:22 index.sk.html
> -rw-rw-r-- 1 akshita akshita 18383 Jul 23 15:22 index.sr.html
> -rw-rw-r-- 1 akshita akshita 15657 Jul 23 15:22 index.sv.html
> -rw-rw-r-- 1 akshita akshita 27570 Jul 23 15:22 index.uk.html
> -rw-rw-r-- 1 akshita akshita 15630 Jul 23 15:22 index.zh_cn.html
> -rw-rw-r-- 1 akshita akshita 15629 Jul 23 15:22 index.zh_tw.html
--
http://fam-tille.de
Reply to: