envy
envy copied to clipboard
distutils2
Explore using setup.cfg instead of a new file.
:clap:
that is a really intriguing idea! do you plan on using the setup.py for the requirements or would you still define them in the setup.cfg. I'm not quite familiar with setup.cfg so I'm not sure if install_requires can be specified in it. Would it be able to handle conditional requirements? Btw, I've made quite a bit of headway on my own very similar project which you are more than welcome to cannibalize for your needs :-D! The project is called virtstrap
Thanks! I think so too.
My idea would be to define the "range" of requirements and in setup.cfg. Envy could then generate a requirements.txt file from it, with all pinned versions.
https://github.com/iguananaut/d2to1
Not sure if you've seen this before, but this project seems semi-relevant to the whole idea of using setup.cfg. I did some research on the idea last night. Definitely seems doable. I was thinking of implementing a branch on virtstrap that would use it :-D. Sorry to steal the idea. I think it's wonderful!
Turns out there's already a requires-python in setup.cfg.
And requires-external for other uses. http://www.python.org/dev/peps/pep-0345/#requires-python