anaconda environment?

[Casyfill]

Hey, that looks like a great project and very close to what we were looking for.
I understand why you guys ditched any environments, but still - is there any way to use lore with existing / specific conda environment (or do you think it is relatively simple to PR this feature?)

[montanalow]

There isn't currently a way to specify a pre-existing virtual env, although it wouldn't take much more than adding a new environment variable and using that instead of searching for it. Is that what you had in mind?

[Casyfill]

yes! but also - can lore spin out another conda environment, instead of local python?

[montanalow]

Lore doesn't use local python per se. It uses pyenv to build whatever version of python is specified in runtime.txt or init --python-version. Are you advocating for using conda as the python installation service rather than pyenv? It might help me understand the motivation if you added more context.

[Casyfill]

Yes, exactly. Well Not so much advocating as to wondering if it is feasible/hard to replace one with another

…

On Fri, Aug 17, 2018 at 17:55 Montana Low ***@***.***> wrote: Lore doesn't use local python per se. It uses pyenv to build whatever version of python is specified in runtime.txt or init --python-version. Are you advocating for using conda as the python installation service rather than pyenv? It might help me understand the motivation if you added more context. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#115 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACjTpdxAQPfmN6XT58MKW0yVimAhGCx3ks5uRzvfgaJpZM4WBvaw> .

[montanalow]

Part of the motivation for Lore is to abstract away virtualenv maintenance, so developers don't need to worry about conda vs pyenv etc. There isn't currently any support for conda/environment.yaml or Pipfile, but it wouldn't be impossible to add. For example, do you think Lore should check for Pipfile, environment.yaml or requirements.txt and use whichever it finds first to setup the virtualenv?

[Casyfill]

Yes, that makes sense. It would be also nice to specify/pin miniconda version (or just have it as an option)

…

On Fri, Aug 17, 2018 at 22:33 Montana Low ***@***.***> wrote: Part of the motivation for Lore is to abstract away virtualenv maintenance, so developers don't need to worry about conda vs pyenv etc. There isn't currently any support for conda/environment.yaml or Pipfile, but it wouldn't be impossible to add. For example, do you think Lore should check for Pipfile, environment.yaml or requirements.txt and use whichever it finds first to setup the virtualenv? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#115 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACjTpaMyYrS6l4RhmthpFHshD8Dq2A0Xks5uR3zngaJpZM4WBvaw> .

[mturok]

Out of curiosity, if you aren't using conda explicitly, are you able to pick up the mkl dependencies for numpy in some other fashion? (eg, specific wheels?)