2 ms·
Does anyone have a good writeup on the workflow for contributing to open source Python projects? I often fix small bugs, but it's a pain because I usually insta
by chatmasta 12y ago
Does anyone have a good writeup on the workflow for contributing to open source Python projects? I often fix small bugs, but it's a pain because I usually install via pip, then when I realize there is a bug, and fixing it myself is the fastest way to resolve it, I have to go out of my way to do so. I have to remove the pip package, fork the original repo, clone it into the repository of my current project (where I would rather it not be) and load it directly as a module. Then I can edit the source code, find the bug, fix, commit, and pull request. But at that point my project's code depends on its own local copy of the buggy repo until the upstream repo finally merges the fix (if ever).
If anyone has a better workflow for fixing ad hoc bugs you discover while integrating an open source library into your project, I would love to hear it.
- kmike84 12y agoIf you have a public repository anywhere (e.g. you've forked a project on github) then you can add a specific git commit to the requirements instead of pypi version. See https://pip.pypa.io/en/latest/reference/pip_install.html#vcs-support https://pip.pypa.io/en/latest/reference/pip_install.html#vcs...
- chatmasta 12y agoExactly what I was looking for. This is why I come to HN. Very clever. Thanks.