Well, if you really wanted to go nuts with this, you could re-write it as a C program that's linked to libcurl. I have a couple of C programs that already know how to talk filelist. It shouldn't be much harder to add functionality to make pkgrecv work. Parsing manifests is probably the trickiest part.
However, it probably makes more sense to keep all of this in Python for now. -j On Fri, Jul 11, 2008 at 02:53:16PM -0700, Dan Price wrote: > On Fri 11 Jul 2008 at 02:42PM, [EMAIL PROTECTED] wrote: > > > > Should that exception handler be tighter? Danek-- isn't this the sort > > > > of exception handler that gets us into trouble when someone does > > > > e.g. ctrl-c during an operation? > > > > > > Yup. But since all the surrounding exception handlers are doing exactly > > > the same thing, I wasn't going to bring (raise?) that up. We're going to > > > want to do a bunch of exception cleanup in the code eventually. Not sure > > > what the priority on that is. Probably should be higher than it's likely > > > to be. :-/ > > > > Well, this is just a utility for capturing the contents of packages, so > > you can move them around. I would defer dealing with making the > > exception handlers more specific until we have a reason to do so. > > > > Most command-line utilities written in C have similar error handling: > > What I dislike about our code is that if you ctrl-c it, you get an > exit code of 0. > > The exception hierarchy is just annoying for now in python. Hopefully this > will get fixed in 2.6. When that happens we can then do: > > except StandardError > > -dp > > -- > Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - > blogs.sun.com/dp > _______________________________________________ > 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
