Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Update docs to reflect latest buildpacks and Python 2 build specification

See original GitHub issue

Post merge of #284 and #277, we should test the various combinations of Python 2 build specifications to make sure that we can articulate which files take precedence when any combination of these:

runtime.txt
requirements.txt
environment.yml

It would be helpful to document these combinations and results and also update any related binder-examples builds.

cc @betatim @choldgraf @GladysNalvarte

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:8 (4 by maintainers)

Top GitHub Comments

2reactions

jzf2101commented, Jul 2, 2018

I’ve put conflicting python version in runtime.txt and environment.yml and dependencies in environment.yml and requirement.txt and can confirm that enviornment.yml supercedes all other files.

In fact, if environment.yml does not specify a version of Python- it defaults to 3.6 even when a runtime.txt says a different version.

0reactions

betatimcommented, Jul 2, 2018

I think all what you said is correct in terms what wins over what.

Most of this is because we have a list of build packs which are tried in turn till one says “Jupp I match” and then that buildpack is used. Which is why I was saying in #338 that we should be careful with the “composable” thing because really there is only one buildpack that wins in the end, but that buildpack might support using several config files 😕