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

Compile files ending in .py not those ending in py #1163

Merged
merged 1 commit into from
Aug 2, 2016

Conversation

mingwandroid
Copy link
Contributor

Otherwise files like h5copy get found and the build will fail

Otherwise files like h5copy get found and the build will fail
@codecov-io
Copy link

Current coverage is 46.6% (diff: 100%)

Merging #1163 into master will not change coverage

@@             master      #1163   diff @@
==========================================
  Files            43         43          
  Lines          5672       5672          
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
  Hits           2642       2642          
  Misses         3030       3030          
  Partials          0          0          

Powered by Codecov. Last update 0181cf3...0f4b1c1

@msarahan
Copy link
Contributor

msarahan commented Aug 2, 2016

Yikes, good catch. That was silly of me. Does it actually kill the build, though? I thought that with #1146 it would barf but not die?

I'm asking because this is the difference between merging and doing another 1.21.x release, or just merging and proceeding to 2.0.

@msarahan msarahan merged commit e79f56d into conda:master Aug 2, 2016
msarahan added a commit to msarahan/conda-build that referenced this pull request Aug 2, 2016
Compile files ending in `.py` not those ending in `py`
@github-actions github-actions bot added the locked [bot] locked due to inactivity label May 14, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 14, 2022
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.

3 participants