[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: why doesn't yum cache anything?



>   using the reader at the C level, this include decompressing the archive
> and walking though all nodes. The main cost is to turn the parsed data into
> Python's internal representation as I said.
> 
> > than wouldn't be useful to 
> > implement that small portion in C? or it isn't so small part?
> 
>   The string interning is in the Python lib, probably in C as it's a C API
> as far as I can tell. And no I din't looked at python internal code.

I'm talking from ignorance here:
 Would it be possible to speed up the string interning by providing your
own __repr__ methods in the libxml2 python module?

-sv




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]