Re: how to get list of debianmed packages
Hi Ole,
On Tue, Mar 15, 2016 at 01:22:15PM +0100, Ole Streicher wrote:
> > File "[...]/blendsmarkdown.py", line 114, in MarkupString
> > % (elem, pkg, lang, 'debug-string', str(err)))
> > TypeError: not all arguments converted during string formatting
> >
> > This does not happen when rendering debian-astro.
>
> That is a stupid bug introduced by me ('%' has higher priority than
> '+'). I fixed this in the repository now. Sorry.
No need to sorry at all. :-)
> However, this happens only if there is a unicode error -- I think this
> is the last appeareance of UnicodeError. I will check why the
> UnicodeError actually appears here in debian-med. I would guess that
> this is an encoding problem in one of the DebianMed tasks.
The actual unicode character is removed now from the tasks file. We
need to wait for the next cron job to gather this in UDD.
> > If you have both outputs ("classic" and "udd") you can compare these
> > using test_output_udd.py.
> >
> > The main issue I was working on is that the prospective packages which
> > are not yet in VCS (== exclusively mentioned inside the tasks files) are
> > not yet rendered. The data are gathered into UDD properly and are
> > residing inside the table blends_unknown_packages but not rendered
> > yet.
>
> So this is still not implemented in blendstasktools_udd.py?
Yes. This is what I planned to do past Christmas - now its close to
Easter. Everybody who intends to beat me with this is perfectly
welcome. ;-)
(I'm currently busy with helping my son with some publication and
thus my spare time is occupied by private stuff ...)
> >> The UDD ist quite difficult to use. Look into blendstasktools.py to see
> >> what an amount to code is needed to get it into a usable form. In
> >> contrary, the web pages could be generated from a JSON file with just
> >> applying the template.
> >
> > I agree to some extend but I'd volunteer to inject handy SQL functions
> > into UDD to reduce complexity for certain tasks.
>
> SQL is just a difficult beast, especially for non-daily users. Having
> the information available as JSON as well would make it much easier to
> develop customized frontends.
I'm perfectly fine with this.
> And, offering the information of our blends pages also as JSON would IMO
> help *us* to separate the data model from the presentation; in the
> moment they are somehow mixed a bit.
ACK. I hope I never made the impression that I'm against progress in
our tools. ;-) I just wanted to explain why I personally have set my
preferences differently when I worked on this in the past.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: