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

[DOC] Inconsistent double tick quotes in docstrings #809

Open
zy18811 opened this issue Oct 9, 2023 · 8 comments
Open

[DOC] Inconsistent double tick quotes in docstrings #809

zy18811 opened this issue Oct 9, 2023 · 8 comments
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers

Comments

@zy18811
Copy link
Contributor

zy18811 commented Oct 9, 2023

Describe the issue linked to the documentation

Single ticks render as italics while double ticks render as code in the api docs, e.g. int v.s. int. Various methods use this inconsistently, example from the HIVECOTE 2.0 docs below:

Docstring for random_state uses single ticks (italics) for all references to code, i.e. int, RandomState, and None.

image

Docstring for n_jobs uses double ticks for -1 to represent it referring to code.

image

Suggest a potential alternative/fix

Select preferred approach out of single and double ticks for referring to code in docstrings and apply consistently throughout aeon.

@zy18811 zy18811 added the documentation Improvements or additions to documentation label Oct 9, 2023
@TonyBagnall TonyBagnall added the good first issue Good for newcomers label Nov 24, 2023
@TonyBagnall
Copy link
Contributor

I think double ticks is preferable

@adityagh006
Copy link

Hi @TonyBagnall, I'd like to work on this issue. Could you please assign it to me?

@MatthewMiddlehurst
Copy link
Member

Please read our contributor guide. It would be a bit much to do this for the whole package, why not select a module then post here that you will be working on it?

@Val-2608
Copy link

Hi ,I'd like to work on resolving any inconsistencies in the documentation for the regression module.

@AnaghDeshpande
Copy link

Hi, @MatthewMiddlehurst i would like to work on anomaly_detection

@NasheetaFarzana
Copy link

Hello @MatthewMiddlehurst @TonyBagnall. I would like to work on this project. But as a beginner I need your guidance for how to start contributing ( mainly improving the documentation and docstrings ) in the code.

@MatthewMiddlehurst
Copy link
Member

Hi @NasheetaFarzana that depends on how experienced you are really. I would look at our contributing guide on the website. As i mentioned on Slack for stuff such as how to use Git, GitHub, or learning Python we are not the place unfortunetly.

@nMaax
Copy link

nMaax commented Mar 9, 2025

Hi @MatthewMiddlehurst , I noticed some inconsistencies in the segmentation module and would like to work on fixing them. It doesn't seem to me anyone else is working exactly on this module, just wanted to check if I can proceed.

Edit: Already forked and made commits on my fork's branch with all the updates, only thing to do now is the pull request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

8 participants