Skip to content
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

Support for pinning Lua by default #1934

Merged
merged 4 commits into from
Jan 3, 2016
Merged

Support for pinning Lua by default #1934

merged 4 commits into from
Jan 3, 2016

Conversation

alexbw
Copy link
Contributor

@alexbw alexbw commented Jan 2, 2016

This pull request is a small accompaniment for a larger PR in the conda-build repo here: conda/conda-build#719

This pull request pins Lua versions by default, because Lua releases, like Python, do not occur often, but when they do, they often break packages.

@ilanschnell
Copy link
Contributor

Thanks for the PR. Trying to determine the default Lua version by using a subprocess seems slow and brittle, and is probably not something we want to be doing in conda. In particular because only very few people use Lua, but all conda users are going to be affected by this change. As far as I'm concerned, conda (unlike conda-build) should not have any features hard-coded to support special languages. My point of view is that conda is a language (which includes Python) agnostic package manager. Conda-build, on the other hand, may (and does) contain special code to support all sorts of commonly used scenarios.

@alexbw
Copy link
Contributor Author

alexbw commented Jan 2, 2016

Thanks for the comment. Should I hard-code the Lua version? Use of Lua in
conda-build will be severely hampered without some kind of auto-pinning.
Also, the default version does not appear to be actually used, and just
serves as a placeholder to preserve the format of the iterator, so perhaps
the subprocess call can be removed entirely?
On Fri, Jan 1, 2016 at 9:30 PM Ilan Schnell notifications@github.com
wrote:

Thanks for the PR. Trying to determine the default Lua version by using a
subprocess seems slow and brittle, and is probably not something we want to
be doing in conda. In particular because only very few people use Lua, but
all conda users are going to be affected by this change. As far as I'm
concerned, conda (unlike conda-build) should not have any features
hard-coded to support special languages. My point of view is that conda is
a language (which includes Python) agnostic package manager. Conda-build,
on the other hand, may (and does) contain special code to support all sorts
of commonly used scenarios.


Reply to this email directly or view it on GitHub
#1934 (comment).

@alexbw
Copy link
Contributor Author

alexbw commented Jan 3, 2016

Turns out everything but the default version of Python is unused in the "pinning" section of plan.py, so I removed it. This PR is now effectively single line change that will pin only Lua, hopefully that's minimal enough to merge.

@ilanschnell
Copy link
Contributor

It seems a bit strange to me that it should be necessary to set a default version to None, but I certainly wouldn't have a problem merging this one line change anymore.

@alexbw
Copy link
Contributor Author

alexbw commented Jan 3, 2016

I can set it to whatever's most innocuous, but I need something to not
break the iterator:
https://github.com/conda/conda/pull/1934/files#diff-d89048bb7f0ea8668934e579b409f994R340
.
Alternatively, I can comment that line to explain why None is used.
If None is fine, then the merge would be appreciated!

On Sun, Jan 3, 2016 at 10:48 AM, Ilan Schnell notifications@github.com
wrote:

It seems a bit strange to me that it should be necessary to set a default
version to None, but I certainly wouldn't have a problem merging this one
line change anymore.


Reply to this email directly or view it on GitHub
#1934 (comment).

@ilanschnell
Copy link
Contributor

If you add a small comment why None is used, then I'm happy to merge your PR. Thanks

@alexbw
Copy link
Contributor Author

alexbw commented Jan 3, 2016

Done

@github-actions
Copy link

github-actions bot commented Oct 6, 2021

Hi there, thank you for your contribution to Conda!

This pull request has been automatically locked since it has not had recent activity after it was closed.

Please open a new issue or pull request if needed.

@github-actions github-actions bot added the locked [bot] locked due to inactivity label Oct 6, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants