[13:37:58] <will_f> Hi. Installed a package from conda-forge, exported the working environment using `conda list -e > e.yml`, then tried `create -n myenv -c conda-forge -f e.yml` but get lots of conflicts e.g. `backports 1.0 py35_0 -> python 3.5*`. Any ideas?
[15:07:52] <ngoldbaum> will_f: this isn't really the right place to ask - maybe open an issue on the conda-forge issue tracker?
[18:09:33] <laharah_> I was wondering if anyone could tell me if pep 508 declarations work in install_requires sections?
[18:45:15] <tos9> laharah_: I haven't read PEP 508, but I doubt it -- AIUI install_requires is handled by setuptools directly. So if PEP 508 has to do with environment markers and the like, they go in extras_require which pip handles.
[19:04:53] <laharah_> the pep says that it's in use on pip, though I'm not sure where. I'm having trouble getting `:sys_platform=="win32"` to actuall install extra dependencies on windows so was hoping pep 508 would help
[19:15:54] <dstufft> laharah_: I think there's a bug with that, that I might not have released a fix for yet
[19:21:59] <simon_weber> I'm running into a pkg_resources.RequirementParseError in a third party library when dealing with vcs requirements: https://github.com/blue-yonder/devpi-builder/issues/99. Is there a different way of parsing the requirements file that I can recommend to them?
[19:22:15] <simon_weber> their code is here: https://github.com/blue-yonder/devpi-builder/blob/master/devpi_builder/requirements.py
[19:45:08] <laharah_> tos9: thanks for the help, turned out to be a bug in tox