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
Add recipe for xrst (extract rst files and run sphinx) #25198
base: main
Are you sure you want to change the base?
Conversation
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/xrst:
|
There seems to be a problem with the conda-forge version of pyenchant that is caussing some of the test failures; see |
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 ( |
Also remove pyenchant from requirements (not used by conda install).
remove dependency on pyenchant.
I am convinced that the following commit truly passed the test on all the target systems: 0adf204 Waiting for feed back from the review team as per the instructions on |
@conda-forge/help-python, ready for review. |
@conda-forge/help-python |
To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks! |
recipes/xrst/2024.0.0.patch
Outdated
'sphinx', 'toml', 'sphinx-copybutton', # required | ||
'pytest', # need for testing xrst | ||
- 'pyenchant', 'pyspellchecker', # need the one you use | ||
+ 'pyspellchecker', # need the one you use |
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.
Since deps are specified in the meta.yaml
it's not necessary to patch them in the setup.py
... unless it's to enable pip check
to work.
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.
I don't think there are any issues which should prevent merging, however I don't have merge rights myself...
The following text appears in meta.yaml:
As I understand, the commands above instruct conda-forge to use pip to install the python files. |
It uses pip to install just the package itself (it passes The dependencies used are those specifiedin the |
Thanks for the clarification. I made the suggested changes; see |
I have been looking into fixing the pyenchant problem so that xrst can use it for a spell checker; see In any event, xrst will not be able to use pyenhant on windows because enchant is not available on windows; see
So the solution here (not using pyenchant in the conda-forge install of xrst) may be the simplest because it makes xrst consistent for all platforms. |
Can you please create your recipe with grayskull once and see if that passes? If it fails on windows because there is a missing dependency, you can just ignore that. https://github.com/conda/grayskull |
I created a recipe for xrst using the command
I then ran the command:
and got the following error message:
Note that Looking at As noted in at the top of xrst/meta.yaml, in the pull request:
|
|
In xrst/meta.yaml (generaged by grayskull) I changed
If I execute
If I execute
|
Purpose of xrst:
https://xrst.readthedocs.io/latest/purpose.html
Checklist
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details).