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

Problems with Spyder on Mac with Conda-forge and applaunchservices #17835

Closed
1 of 10 tasks
nerohmot opened this issue May 6, 2022 · 4 comments · Fixed by #18530
Closed
1 of 10 tasks

Problems with Spyder on Mac with Conda-forge and applaunchservices #17835

nerohmot opened this issue May 6, 2022 · 4 comments · Fixed by #18530
Assignees
Milestone

Comments

@nerohmot
Copy link

nerohmot commented May 6, 2022

Issue Report Checklist

  • Searched the issues page for similar reports
  • Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
  • Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
  • Could not reproduce inside jupyter qtconsole (if console-related)
  • Tried basic troubleshooting (if a bug/error)
    • Restarted Spyder
    • Reset preferences with spyder --reset
    • Reinstalled the latest version of Anaconda
    • Tried the other applicable steps from the Troubleshooting Guide
  • Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description

We want to release a plugin to spyder on conda-forge.
Our package must be a noarch type with the twist that python >= 3.8.
conda-forge insists and we run pip check in the recipe (which makes a lot of sense), however this fails because spyder relays on applaunchservices for OSX, but not all it's dependencies are in conda-forge ☹️ and thus the check fails as follows:

image

Fortunately for us, @goanpeca is the conda-forge reviewer, so I asked him if he could approve our feedstock when I do the following in or recipe:

image

This will get me up and running, however the cleaner way would be if we take the applaunchservices out of spyder's conda-forge recipe, this way others (like this guy from PROCITEC ?) will not have the same problem as us.

All plugins can then enable the normal pip check without selectors (and discussions with conda-forge) and once the applauchservices work again, then we can enable it again and support for spyder on OSX under CONDA, the plugin recipies don't have to do anything anymore (presumed that the plugins are noarch)

Could this be done in the upcomming 5.3.1 release already ?

@ccordoba12
Copy link
Member

Thanks for reporting @nerohmot! We'll take a look at this in our next release.

@nerohmot
Copy link
Author

nerohmot commented May 7, 2022

🙏

@mrclary
Copy link
Contributor

mrclary commented May 8, 2022

@impact27 is looking into this already. This is not a Spyder issue but an applaunchservices conda packaging issue, AFIK. See impact27/applaunchservices#1

@dalthviz dalthviz changed the title Spyder on OSX with conda-forge Spyder on OSX with conda-forge and applaunchservices May 16, 2022
@dalthviz dalthviz assigned andfoy and unassigned ccordoba12 May 16, 2022
@dalthviz dalthviz removed this from the v5.3.1 milestone May 16, 2022
@ccordoba12 ccordoba12 added this to the v5.3.1 milestone May 21, 2022
@ccordoba12
Copy link
Member

We can fix this on our side by requiring a more recent version of applaunchservices.

@ccordoba12 ccordoba12 assigned ccordoba12 and unassigned andfoy May 21, 2022
@ccordoba12 ccordoba12 modified the milestones: v5.3.1, v5.3.2 May 22, 2022
@ccordoba12 ccordoba12 changed the title Spyder on OSX with conda-forge and applaunchservices Problems with Spyder on Mac with Conda-forge and applaunchservices Jul 2, 2022
@dalthviz dalthviz linked a pull request Jul 4, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants