Skip to content
This repository has been archived by the owner on Apr 9, 2020. It is now read-only.

add bldpkg_path_wrapper() #39

Closed
wants to merge 4 commits into from
Closed

add bldpkg_path_wrapper() #39

wants to merge 4 commits into from

Conversation

shadowwalkersb
Copy link

Adds on PR #34 to fix calls to bldpkg_path().

@conda-forge-linter
Copy link

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@pelson
Copy link
Member

pelson commented Dec 14, 2016

If this is still a live PR, then I'm pretty much in favour of merging as is.

@jakirkham
Copy link
Member

Closing and reopening to restart CIs.

@jakirkham jakirkham closed this Dec 16, 2016
@jakirkham jakirkham reopened this Dec 16, 2016
@conda-forge-linter
Copy link

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

config = Config()
fname = bldpkg_path(meta, config)
except TypeError:
# conda-build < 2.0.0 takes a single config argument
Copy link
Member

Choose a reason for hiding this comment

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

We should update this comment because latest conda-build 2 behaves like conda-build 1 and no longer take the config argument.

Copy link
Author

@shadowwalkersb shadowwalkersb Dec 16, 2016

Choose a reason for hiding this comment

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

If conda-build 2 behaves the same, doesn't this PR become unnecessary along with PR #34 ?

Copy link
Member

Choose a reason for hiding this comment

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

There is more to come. Maybe we should take a second look at latest conda-build.

See conda-tools/conda-build-all#68 (comment)

@jakirkham
Copy link
Member

Probably also should rebase to get updated behavior for CircleCI.

@jakirkham
Copy link
Member

AppVeyor won't restart due to GitHub rate limiting. FWIW the message in the AppVeyor console is totally clear on this point.

xref: appveyor/ci#1002 (comment)

@shadowwalkersb
Copy link
Author

Rebased.

@jjhelmus
Copy link
Contributor

In conda-build 2.x the get_output_file_path function from conda_build.api is a better option than using bldpkg_path. Since is is part of the API it should not change without a version increment. Perhaps trying to import this with a fallback to importing bldpkg_path would be a good solution for supporting both conda-build 1 and 2.

@ocefpaf
Copy link
Member

ocefpaf commented Dec 16, 2016

Agreed. I just leaner about get_output_file_path from @mwcraig.

@jakirkham
Copy link
Member

What do you think about @jjhelmus's suggestion above, @shadowwalkersb? Would it be possible to update this PR accordingly?

@shadowwalkersb
Copy link
Author

Will that do ( b89ca05 ) ?

@shadowwalkersb
Copy link
Author

I've figured out the problem with my CircleCI PRs. This should pass, hopefully.

try:
from conda_build.api import get_output_file_path
except ImportError:
from conda_build.build import bldpkg_path as get_output_file_path
Copy link
Member

Choose a reason for hiding this comment

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

👍

@shadowwalkersb
Copy link
Author

Anything else here?

@jakirkham
Copy link
Member

Thanks @shadowwalkersb. However I think this is now unnecessary as we no longer support conda-build 1 and are working on supporting conda-build 3 (potentially dropping conda-build 2 in the process). Hence am closing this out. Feel free to let us know if you think otherwise.

@jakirkham jakirkham closed this Nov 30, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants