Look at my #Python dev cred go down the drain:
- Package A setup.py requires Package B>=1.0
- Package B is released until v1.0 but there's a new commit in master that solves an unrelated problem (so it's kinda v1.0+) and I need to use this commit
How do I convince pip and setup.py that Package B (installed with git+https etc) is *actually* later than 1.0?
Can anybody help?
@pgcd use `pip -e` on B to install an editable version of B. And edit the version in place?
Not sure what `setup.py` will do tho.
@pgcd or use `pip -e` and install the branch of B that is newer.
In PIP requirements.txt or on cli you can specify a branch with git+https with `@` syntax.
@pgcd Let the wrong one install and then immediately afterwards, install `pip install correct-version`
@mistersql I can't see this working in a pipeline, though (but that's probably my lack of knowledge)
@pgcd let package b maintainers know the change is significant and ask for a version tag 1.0.1 or whatever they want. that’s why versioning exists!
@BenjaminHimes i might have been added as co-maintainer so this is what will happen, but I wondered if there's a quick and dirty way of dealing with this "on my own".
@pgcd great! I don’t know of any quick n dirty route in this case, b/c I don’t know squat about python packaging, just a thought on the “human element” when it comes to this sort of thing. (which I do have a lot of experience with : )