Skip to content

Pass build env python limits to config object #2627

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Feb 13, 2017
Merged

Conversation

agjohnson
Copy link
Contributor

  • Pass in build env python limitations to config
  • Exposes parsing error to user on build output

Requires readthedocs/readthedocs-build#21

* Pass in build env python limitations to config
* Exposes parsing error to user on build output
@agjohnson agjohnson added PR: work in progress Pull request is not ready for full review PR: ready for review labels Feb 3, 2017
Copy link
Member

@ericholscher ericholscher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

'readthedocs/build:16.04': {
'python': {'supported_versions': [2, 2.7, 3, 3.5]},
},
'readthedocs/build:beta': {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wonder if this should be given a more specific name? Seems like we'll want to do stuff over time where beta isn't really reflective of, and we don't want it to conflict.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking about naming schemes myself, however I was considering how to make names more generic. I don't think it's important to have a 16.04 branch of names and a 14.04 branch of images. Perhaps we adopt semver versioning instead? I'll leave this for now, we can discuss versioning in the docker-images repo

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@agjohnson
Copy link
Contributor Author

I updated the tests to do a full test of our configuration, instead of just testing the readthedocs-build implementation. It should be pretty close to parity, but it did uncover a bug in python version detection. Might be worth a once over

@ericholscher
Copy link
Member

Looks good.

@agjohnson agjohnson merged commit dced32b into master Feb 13, 2017
@agjohnson agjohnson deleted the python-pyenv branch February 13, 2017 22:11
@agjohnson agjohnson removed PR: ready for review PR: work in progress Pull request is not ready for full review labels Feb 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants