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

Separate build for use in testing? #110

Closed
dopplershift opened this issue Feb 8, 2017 · 8 comments
Closed

Separate build for use in testing? #110

dopplershift opened this issue Feb 8, 2017 · 8 comments

Comments

@dopplershift
Copy link
Member

So for testing, matplotlib builds against an internal copy of freetype 2.6.1. Are there any votes against me adding a branch and build creating conda-forge packages linked against that copy? (They would obviously go under a different label.)

This would help me a great deal doing CI on metpy and its plotting tests, which have now broken on AppVeyor due to the move to freetype 2.7.

@ocefpaf
Copy link
Member

ocefpaf commented Mar 23, 2017

I don't have anything against it. Let me know if you have the rights to create the branch.

(Sorry it took so long for me to notice this! Maybe you no longer need this 😳)

dopplershift added a commit to dopplershift/matplotlib-feedstock that referenced this issue Apr 24, 2017
dopplershift added a commit to dopplershift/matplotlib-feedstock that referenced this issue May 3, 2017
@ocefpaf
Copy link
Member

ocefpaf commented Aug 10, 2017

@dopplershift I guess this can be closed, right? If not please re-open.

@ocefpaf ocefpaf closed this as completed Aug 10, 2017
@dopplershift
Copy link
Member Author

Kinda. I can't get them on windows until 2.1 releases...

@dopplershift
Copy link
Member Author

Ok, 2.1 is out so I should be able to get around to making this work now.

@QuLogic
Copy link
Member

QuLogic commented Sep 25, 2018

Not sure about Windows, but looks like it needs an update for mpl 3?

@ocefpaf
Copy link
Member

ocefpaf commented Nov 12, 2018

Can we close this issue? Looks like SciTools/cartopy#1130 has everything you nee, right?

@dopplershift
Copy link
Member Author

I'll close it out once #192 is in and I confirm all the packages seem fine. I was noticing some weird issues on my mac, probably related to what was fixed in #191.

@dopplershift
Copy link
Member Author

Everything looks good here now.

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

No branches or pull requests

3 participants