Summary: | portageq should be importable by python | ||
---|---|---|---|
Product: | Portage Development | Reporter: | michael <michael> |
Component: | Core - External Interaction | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
michael@smith-li.com
2010-02-07 17:52:46 UTC
Most of the functions in portageq are very simple wrappers around the existing public portage API. Which functions are you interested in using? If they are small functions that use the public API then you may just want to copy the code from portageq and use the public API directly. (In reply to comment #1) > Most of the functions in portageq are very simple wrappers around the existing > public portage API. True, and now that I've read through what I thought was a medium-sized function, it turns out most of what it's doing is validating inputs. I can do that myself, I guess. Thanks! (To answer your question, I'm not entirely sure which features I would've ended up using, but I'm looking for a way to compare names from pypi to those in portage. My goal is to write a g-cpan workalike for pypi.) (In reply to comment #2) > My goal is to write a g-cpan workalike for pypi. You might check g-pypi: http://code.google.com/p/g-pypi/ (In reply to comment #3) > You might check g-pypi: http://code.google.com/p/g-pypi/ Heehee. Opening a bug always finds me the answer I'm looking for. Thanks! |