-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
added recipe for semi-ate-spyder #18853
Conversation
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 ( |
Hi! This is the friendly automated conda-forge-linting service. I was trying to look for recipes to lint for you, but couldn't find any. |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/semi-ate-spyder:
|
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/semi-ate-spyder:
|
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 ( |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/semi-ate-spyder:
|
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 ( |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/semi-ate-spyder:
|
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/semi-ate-spyder:
|
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 ( |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/semi-ate-spyder:
|
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/semi-ate-spyder:
|
@goanpeca |
I also asked @ccordoba12 for a 'cleaner' solution from spyder side in spyder-ide/spyder#17835, but I would appreciate it if we can proceed as proposed, and not have to wait for the cleaner solution 😇 |
Since it’s noarch it will only be built on Linux in the feedstock and we can ignore the OSX failure here. |
Co-authored-by: Daniel Ching <carterbox@users.noreply.github.com>
@carterbox, you would think so, however when applying your suggestion I get : |
@nerohmot I meant you could remove those lines instead of leaving commented :)
Also agree with this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the recipe @nerohmot
@conda-forge/staged-recipes Can we merge now? |
This error does not say that your package requires numpydoc. It says that numpydoc was installed in the test environment and the numpydoc=1.2.1 package is broken. |
Also, you don't need to take screenshots. If you want to quote relevant text, just copy the log text directly. |
There's probably a similar issue with applaunchservices. That package incorrectly specified their dependencies / didn't do pip check in their feedstock, so the pip check error shows up here. Figure out which build of applaunchservices isn't broken and add that as a constraint to your test environment. |
@carterbox, applaunchservices is a Spyder dependency and at the moment we're figuring out how to solve the problem related to it in conda-forge. I think it has to do with some Pyobjc libraries missing, but I haven't had time to take a look at it in depth. So we'd appreciate if this PR could be merged as it is because I think it's not for @nerohmot to sort that out. |
Checklist
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details).