Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
discussion: push capa library to pypi?
See original GitHub issueputting capa on pypi would make it a lot easier for other projects to use its logic.
however, there are at least two concerns:
- rules are not packaged with the library, so users have to bring their own. i think this is ok.
- capa relies on vivisect, which is not on pypi.
(2) is the more interesting discussion. in flare-floss we avoided a release on pypi for this reason. but there was definitely strong interest in it. since the floss release, upstream vivisect isn’t really any closer to being released on pypi.
should we push our vivisect fork to pypi as well as capa? if so, we can use our own package name, maybe wivisect 😄
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:12 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
vivisect on pypi!? https://pypi.org/project/vivisect/#history
@williballenthin I’d like to apologize for the delay in getting vivisect up on pypi proper. At lot of other things have taken priority.
Personally, I would like to avoid any kind of naming collision since it generates confusion down the line. And to put my money where my mouth is: https://github.com/vivisect/vivisect/pull/292 (and test:
pip install -i https://test.pypi.org/simple/ vivisect)As for a py3 port, I’m already wading into those waters and directing more of my efforts towards that. I’ll keep you in the loop on that.