Once we start using filters for l10n and when filters work on set actions (issue 322), then I have no doubt that unicode values for description attributes will be needed. I agree with Dan that this should be fixed now.
Given our future plan to be able to run IPS within Jython as one of the options for portability support, I'm concerned about a mainline piece of client functionality that depends on C code. Can we at least have a failure branch on the import of _fromstr that provides a Python implementation of _fromstr. That would also provide Python source code to represent what the C code is actually doing. Thanks. Tom Danek Duvall wrote: > I'm not completely convinced this should be integrated. In trying to fix > > 2686 action key/value pairs separated by tabs cause parsing problems > > I was unable to find a way to make the action parsing with this > functionality go fast in Python. I tried a bunch of different mechanisms, > but they were all significantly slower than the current code, so I > grudgingly implemented it in C. It's marginally faster than the current > code, but has a bit more functionality. I don't know whether it's really > worth the trouble, though it seems like it might be reasonably easy to use > this to implement a reduced-memory-footprint version of the code, something > I haven't actually tried yet. > > Anyway, comments are welcome. > > http://cr.opensolaris.org/~dduvall/pkg-actions/ > > Thanks, > Danek > _______________________________________________ > pkg-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss > _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
