[00:27:30] <derks> Hello. I have a situation where I have an optional requirement (pyinotify) for Linux, but not available on Darwin (OSX).
[00:27:43] <derks> Trying to avoid having a requirements.linux.txt and requirements.osx.txt
[00:28:18] <derks> actually these are dev requirements ... zero deps in requirements.txt but for development and testing the optional dps are installed
[00:28:37] <derks> any way to simply say "it's ok if this fails to install" in the requirements.txt?
[00:31:49] <carljm> derks: I'm afraid there isn't :/
[00:32:35] <carljm> derks: Your options (as far as I am aware) are to a) leave it out and just tell people on Linux to install it, or b) provide a requirements-linux.txt which just includes `-r base-requirements.txt` and pyinotify
[00:34:30] <derks> yeah i'm already in the b) realm with requirements-dev.txt and requirements-dev-py3.txt ...
[08:45:20] <ronny> you might want to make a installer including python for such a customer
[08:45:44] <ronny> but im not very used to windows envs, things are easier for me in the unix world
[08:46:48] <lansman> this way doesn't suit my needs because i write script for ArcGis using its API and i have to use python interpreter that installed with ArcGis itself
[08:47:32] <lansman> can i use get-pip.py as replacement for pip to install packages?
[08:48:56] <ronny> wheels gan fenerally just be unpacked into the site-packages, but uninstallation of previous versions can be tricky
[08:49:37] <ronny> lansman: bascially im not off-hand aware of a bootstrap pip scenario,
[08:49:56] <lansman> when i call "get-pip.py --help" - it shows me the same params as" pip --help" - it puts some thought that i can use get-pip instead of pip