On Friday 04 July 2003 12:28, Olav Vitters wrote: > On Fri, Jul 04, 2003 at 11:24:51AM -0700, Andi Payn wrote:
> Using urpmf would avoid possible breakage due to a synthesis file format > change. True. But once I write python-URPM they'll both be obsolete anyway. And this tool isn't meant to be permanent; if it is, it should go into the whole suite of urpm checking stuff. > The speed seems to be comparable. If I had gotten yours to work, I might not have bothered writing my new version. > Use "": > urpmf "" --media main-cooker,contrib-cooker --provides --obsoletes Thank you! Now, is there any way to get it to handle a specific list of packages, short of " -o ".join(packages)? > > OK, I'll look into it. Ideally it should provide the equivalent interface > > to perl-URPM, right? > > I think so. It would make it easier to switch from Perl<>Python. This > should convince Mandrake to dump Perl and go with Python. ;) Impossible. To a perl-head, the more ways there are to do something, the better. So, they ought to welcome a python module with open arms, but that doesn't mean they'll want to give up the perl module. If anything, it'll just cause them to ask where the tcl and lua and scheme modules are.... > Pretty soon I'm going to play with Expect again. I've written lots of > Tcl/Expect and while Tcl is fun, I sometimes wanted good and fast > datastructures (like Python has). Some of the Python expect wrappers just help to generate tcl strings (with a little help) and call the interpreter on them. ExpectPy wraps the tcl stuff in python layers (and since the actual interaction is often not the slow part, that's sometimes perfectly fine). But pexpect is pure python, top to bottom. Unless you need 100% compatibility, that's what you want. Plus, that's the one I uploaded, and it'll be easier for you to bend to my will than to download another package and build it yourself.... > The version I posted has the last line wrong (extra indent). Sometimes emailing python scripts can be annoying when you're not using a text-mode mail client. But I love the python whitespace rules anyway (after getting past the initial "ohmigod-what-is-this-FORtran-or-something?!?" reaction, just like every other Python convert I've ever met or heard of). And it's still not as annoying as when Eudora used to sometimes confuse perl scripts with some pre-MIME Mac binary encoding format (which was the version of binhex one later than the one everyone used?). Or [EMAIL PROTECTED]
