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

Fix minor documentation formatting issues in dancing links #34567

Closed
Kerl13 opened this issue Sep 21, 2022 · 8 comments
Closed

Fix minor documentation formatting issues in dancing links #34567

Kerl13 opened this issue Sep 21, 2022 · 8 comments

Comments

@Kerl13
Copy link

Kerl13 commented Sep 21, 2022

Component: documentation

Author: Martin Pépin

Branch: 1c9e627

Reviewer: Frédéric Chapoton

Issue created by migration from https://trac.sagemath.org/ticket/34567

@Kerl13 Kerl13 added this to the sage-9.8 milestone Sep 21, 2022
@Kerl13
Copy link
Author

Kerl13 commented Sep 21, 2022

Author: Martin Pépin

@fchapoton
Copy link
Contributor

Reviewer: Frédéric Chapoton

@fchapoton
Copy link
Contributor

comment:3

ok, feu vert

@vbraun
Copy link
Member

vbraun commented Sep 29, 2022

Changed branch from u/MartinPepin/dancing_links_docs_formatting to 1c9e627

@seblabbe
Copy link
Contributor

Changed commit from 1c9e627 to none

@seblabbe
Copy link
Contributor

comment:5

Is it normal that build/pkgs/configure/checksums.ini and build/pkgs/configure/package-version.txt were modified in this ticket?

@fchapoton
Copy link
Contributor

comment:6

hmm, no. But this is the last commit that Volker has closed before the release.

@Kerl13
Copy link
Author

Kerl13 commented Sep 30, 2022

comment:7

These files are not modified on u/MartinPepin/dancing_links_docs_formatting at least.

By the way, what's the usual practice regarding merged branches? Can I remove the branch on trac or is there a policy to keep them?

vbraun pushed a commit that referenced this issue Mar 26, 2023
    
<!-- Please provide a concise, informative and self-explanatory title.
-->
<!-- Don't put issue numbers in the title. Put it in the Description
below. -->

### 📚 Description

Made small edits to the PR template, making it concise and tidy overall.

<!-- Describe your changes here in detail. -->
<!-- Why is this change required? What problem does it solve? -->
<!-- If this PR resolves an open issue, please link to it here. For
example "Fixes #12345". -->
<!-- If your change requires a documentation PR, please link it
appropriately. -->

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. It should be `[x]` not `[x
]`. -->

- [x] The title is concise, informative, and self-explanatory.
- [x] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation accordingly.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on
Depends on #12345: short description why this is a dependency
Depends on #34567: ...
-->

<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
    
URL: #35141
Reported by: Kwankyu Lee
Reviewer(s): Kwankyu Lee, Tobias Diez
vbraun pushed a commit that referenced this issue Apr 6, 2023
    
<!-- Please provide a concise, informative and self-explanatory title.
-->
<!-- Don't put issue numbers in the title. Put it in the Description
below. -->
<!-- For example, instead of "Fixes #12345", use "Add a new method to
multiply two integers" -->

### 📚 Description

Partial fix for pycodestyle E221, done using autopep8.

E221 multiple spaces before operator

<!-- Describe your changes here in detail. -->
<!-- Why is this change required? What problem does it solve? -->
<!-- If this PR resolves an open issue, please link to it here. For
example "Fixes #12345". -->
<!-- If your change requires a documentation PR, please link it
appropriately. -->

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. It should be `[x]` not `[x
]`. -->

- [x] The title is concise, informative, and self-explanatory.
- [x] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation accordingly.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on
- #12345: short description why this is a dependency
- #34567: ...
-->

<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
    
URL: #35355
Reported by: Frédéric Chapoton
Reviewer(s): Matthias Köppe
vbraun pushed a commit that referenced this issue Apr 6, 2023
    
<!-- Please provide a concise, informative and self-explanatory title.
-->
<!-- Don't put issue numbers in the title. Put it in the Description
below. -->
<!-- For example, instead of "Fixes #12345", use "Add a new method to
multiply two integers" -->

### 📚 Description

The update #35184 broke the docs
upload. Hopefully this is fixed with this PR.

<!-- Describe your changes here in detail. -->
<!-- Why is this change required? What problem does it solve? -->
<!-- If this PR resolves an open issue, please link to it here. For
example "Fixes #12345". -->
<!-- If your change requires a documentation PR, please link it
appropriately. -->

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. It should be `[x]` not `[x
]`. -->

- [x] The title is concise, informative, and self-explanatory.
- [x] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation accordingly.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on
- #12345: short description why this is a dependency
- #34567: ...
-->

<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
    
URL: #35356
Reported by: Tobias Diez
Reviewer(s): Dima Pasechnik, Kwankyu Lee
vbraun pushed a commit that referenced this issue Apr 6, 2023
    
<!-- Please provide a concise, informative and self-explanatory title.
-->
<!-- Don't put issue numbers in the title. Put it in the Description
below. -->
<!-- For example, instead of "Fixes #12345", use "Add a new method to
multiply two integers" -->

### 📚 Description

<!-- Describe your changes here in detail. -->
Follow-up from #35322.
<!-- Why is this change required? What problem does it solve? -->
<!-- If this PR resolves an open issue, please link to it here. For
example "Fixes #12345". -->
<!-- If your change requires a documentation PR, please link it
appropriately. -->

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. It should be `[x]` not `[x
]`. -->

- [x] The title is concise, informative, and self-explanatory.
- [ ] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation accordingly.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on
- #12345: short description why this is a dependency
- #34567: ...
-->

<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
    
URL: #35366
Reported by: Matthias Köppe
Reviewer(s): Gonzalo Tornaría
vbraun pushed a commit that referenced this issue Apr 6, 2023
    
<!-- Please provide a concise, informative and self-explanatory title.
-->
<!-- Don't put issue numbers in the title. Put it in the Description
below. -->
<!-- For example, instead of "Fixes #12345", use "Add a new method to
multiply two integers" -->

### 📚 Description

This is a follow-up on:
- #35110

As preparation for #35322, which is changing more packages to implicit
namespace packages, we remove `.all` imports from these packages
throughout the Sage library.

This is part of:
- #29705

<!-- Describe your changes here in detail. -->
<!-- Why is this change required? What problem does it solve? -->
<!-- If this PR resolves an open issue, please link to it here. For
example "Fixes #12345". -->
<!-- If your change requires a documentation PR, please link it
appropriately. -->

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. It should be `[x]` not `[x
]`. -->

- [x] The title is concise, informative, and self-explanatory.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation accordingly.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on
- #12345: short description why this is a dependency
- #34567: ...
-->
- Depends on #35418
- Depends on #35358
<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
    
URL: #35372
Reported by: Matthias Köppe
Reviewer(s): Gonzalo Tornaría
vbraun pushed a commit that referenced this issue Apr 6, 2023
    
<!-- Please provide a concise, informative and self-explanatory title.
-->
<!-- Don't put issue numbers in the title. Put it in the Description
below. -->
<!-- For example, instead of "Fixes #12345", use "Add a new method to
multiply two integers" -->

### 📚 Description
openblas 0.3.22 is broken, see:
- #35371
- scipy/scipy#18208
- OpenMathLib/OpenBLAS#3976

We reject it.

<!-- Describe your changes here in detail. -->
<!-- Why is this change required? What problem does it solve? -->
<!-- If this PR resolves an open issue, please link to it here. For
example "Fixes #12345". -->
<!-- If your change requires a documentation PR, please link it
appropriately. -->

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. It should be `[x]` not `[x
]`. -->

- [x] The title is concise, informative, and self-explanatory.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation accordingly.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on
- #12345: short description why this is a dependency
- #34567: ...
-->

<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
    
URL: #35377
Reported by: Matthias Köppe
Reviewer(s): John H. Palmieri
vbraun pushed a commit that referenced this issue Apr 6, 2023
    
<!-- Please provide a concise, informative and self-explanatory title.
-->
<!-- Don't put issue numbers in the title. Put it in the Description
below. -->
<!-- For example, instead of "Fixes #12345", use "Add a new method to
multiply two integers" -->

### 📚 Description

<!-- Describe your changes here in detail. -->
<!-- Why is this change required? What problem does it solve? -->
<!-- If this PR resolves an open issue, please link to it here. For
example "Fixes #12345". -->
<!-- If your change requires a documentation PR, please link it
appropriately. -->
`matrix_modn_dense_float.pyx` had single backticks in one of the
docstrings which was causing it to render as LaTeX text, while it was
intended to be monospace formatted. The missing backticks are added to
fix this.

Fixes #35363

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. It should be `[x]` not `[x
]`. -->

- [x] The title is concise, informative, and self-explanatory.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [x] I have updated the documentation accordingly.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on
- #12345: short description why this is a dependency
- #34567: ...
-->

<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
    
URL: #35382
Reported by: Karan Handa
Reviewer(s): Matthias Köppe
vbraun pushed a commit that referenced this issue Apr 6, 2023
    
<!-- Please provide a concise, informative and self-explanatory title.
-->
<!-- Don't put issue numbers in the title. Put it in the Description
below. -->
<!-- For example, instead of "Fixes #12345", use "Add a new method to
multiply two integers" -->

### 📚 Description

<!-- Describe your changes here in detail. -->
The source tarballs made by `make dist` contain a git repository.
We update the remotes.
<!-- Why is this change required? What problem does it solve? -->
<!-- If this PR resolves an open issue, please link to it here. For
example "Fixes #12345". -->
As discussed in https://groups.google.com/g/sage-devel/c/TsHnvmkdrR8
<!-- If your change requires a documentation PR, please link it
appropriately. -->

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. It should be `[x]` not `[x
]`. -->

- [x] The title is concise, informative, and self-explanatory.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation accordingly.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on
- #12345: short description why this is a dependency
- #34567: ...
-->

<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
    
URL: #35384
Reported by: Matthias Köppe
Reviewer(s): John H. Palmieri
vbraun pushed a commit that referenced this issue Apr 6, 2023
    
<!-- Please provide a concise, informative and self-explanatory title.
-->
<!-- Don't put issue numbers in the title. Put it in the Description
below. -->
<!-- For example, instead of "Fixes #12345", use "Add a new method to
multiply two integers" -->

### 📚 Description

<!-- Describe your changes here in detail. -->
Adding the command `sage --tox -e cython-lint`.
See https://pypi.org/project/cython-lint/

There are many failures, so it is not run by default.
<!-- Why is this change required? What problem does it solve? -->
<!-- If this PR resolves an open issue, please link to it here. For
example "Fixes #12345". -->
<!-- If your change requires a documentation PR, please link it
appropriately. -->

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. It should be `[x]` not `[x
]`. -->

- [x] The title is concise, informative, and self-explanatory.
- [x] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [x] I have updated the documentation accordingly.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on
- #12345: short description why this is a dependency
- #34567: ...
-->

<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
    
URL: #35385
Reported by: Matthias Köppe
Reviewer(s): Frédéric Chapoton
vbraun pushed a commit that referenced this issue Apr 6, 2023
    
In sage/src/sage/libs/eclib/mwrank.pyx
Line 843 should read 'minumum' instead of 'minimum'.

<!-- Please provide a concise, informative and self-explanatory title.
-->
<!-- Don't put issue numbers in the title. Put it in the Description
below. -->
<!-- For example, instead of "Fixes #12345", use "Add a new method to
multiply two integers" -->

### 📚 Description

<!-- Describe your changes here in detail. -->
<!-- Why is this change required? What problem does it solve? -->
<!-- If this PR resolves an open issue, please link to it here. For
example "Fixes #12345". -->
<!-- If your change requires a documentation PR, please link it
appropriately. -->

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. It should be `[x]` not `[x
]`. -->

- [x] The title is concise, informative, and self-explanatory.
- [x] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation accordingly.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on
- #12345: short description why this is a dependency
- #34567: ...
-->

<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
    
URL: #35390
Reported by: yukibl
Reviewer(s): Matthias Köppe
vbraun pushed a commit that referenced this issue Apr 6, 2023
    
<!-- Please provide a concise, informative and self-explanatory title.
-->
<!-- Don't put issue numbers in the title. Put it in the Description
below. -->
<!-- For example, instead of "Fixes #12345", use "Add a new method to
multiply two integers" -->

### 📚 Description

<!-- Describe your changes here in detail. -->
<!-- Why is this change required? What problem does it solve? -->
<!-- If this PR resolves an open issue, please link to it here. For
example "Fixes #12345". -->
<!-- If your change requires a documentation PR, please link it
appropriately. -->

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. It should be `[x]` not `[x
]`. -->

- [x] The title is concise, informative, and self-explanatory.
- [ ] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [x] I have created tests covering the changes.
- [ ] I have updated the documentation accordingly.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on
- #12345: short description why this is a dependency
- #34567: ...
-->

<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
    
URL: #35405
Reported by: Marc Mezzarobba
Reviewer(s): Matthias Köppe
vbraun pushed a commit that referenced this issue Apr 6, 2023
    
<!-- Please provide a concise, informative and self-explanatory title.
-->
<!-- Don't put issue numbers in the title. Put it in the Description
below. -->
<!-- For example, instead of "Fixes #12345", use "Add a new method to
multiply two integers" -->

### 📚 Description

fix all pep8 E303 warning in the folders whose name starts with the
letter m

purely done with autopep8:

```
$ autopep8 -i --select=E303 src/sage/m*/*.py
$ autopep8 -i --select=E303 src/sage/m*/*/*.py
```

<!-- Describe your changes here in detail. -->
<!-- Why is this change required? What problem does it solve? -->
<!-- If this PR resolves an open issue, please link to it here. For
example "Fixes #12345". -->
<!-- If your change requires a documentation PR, please link it
appropriately. -->

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. It should be `[x]` not `[x
]`. -->

- [x] The title is concise, informative, and self-explanatory.
- [x] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation accordingly.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on
- #12345: short description why this is a dependency
- #34567: ...
-->

<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
    
URL: #35409
Reported by: Frédéric Chapoton
Reviewer(s): David Coudert
vbraun pushed a commit that referenced this issue Apr 6, 2023
    
<!-- Please provide a concise, informative and self-explanatory title.
-->
<!-- Don't put issue numbers in the title. Put it in the Description
below. -->
<!-- For example, instead of "Fixes #12345", use "Add a new method to
multiply two integers" -->

### 📚 Description

Follow-up from #35056. Currently no
codecov reports are displayed because the doc deployment workflow is
failing and codecov by default only adds its checks if all other checks
are passing. We change this setting so that codecov checks are always
added, regardless of other failing tests.

<!-- Describe your changes here in detail. -->
<!-- Why is this change required? What problem does it solve? -->
<!-- If this PR resolves an open issue, please link to it here. For
example "Fixes #12345". -->
<!-- If your change requires a documentation PR, please link it
appropriately. -->

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. It should be `[x]` not `[x
]`. -->

- [x] The title is concise, informative, and self-explanatory.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation accordingly.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on
- #12345: short description why this is a dependency
- #34567: ...
-->

<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
    
URL: #35412
Reported by: Tobias Diez
Reviewer(s): Kwankyu Lee, Matthias Köppe, Tobias Diez
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 1, 2025
    
Similarly to sagemath#39216, we avoid the conversion to `short_digraph` when the
input graph is an instance of `StaticSparseBackend`.

Furthermore, we use the new `PairingHeap_of_n_integers` data structure
(sagemath#39046) instead of a `priority_queue` to emulate a max-heap. This is
slightly faster this way and cleaner.


### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [x] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39217
Reported by: David Coudert
Reviewer(s): Travis Scrimshaw
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 1, 2025
Looks like the file path has changed some time earlier.

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [x] I have created tests covering the changes. (not applicable)
- [x] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->

URL: sagemath#39238
Reported by: user202729
Reviewer(s): Tobias Diez
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 3, 2025
    
<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->

Use pkg-config to find more dependencies, and add version constraints
(mostly) as specified in the `spkg-configure` scripts.

Now only the packages without pkg-config info use `find_library` (refs
sagemath#39064)

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [ ] The title is concise and informative.
- [ ] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

- sagemath#37447 for the updated conda lock files

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#38993
Reported by: Tobias Diez
Reviewer(s): Antonio Rojas, Dima Pasechnik
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 3, 2025
    
When there is an error during importing `sage.all`, then it is just
hidden but sage's are no longer available. This is very hard to debug
and misleading during development. For this reason the fallback to
`repl.all` is removed.

Furthermore, a ruff exception for "unused imports" is added for all
files, since these files always contains many unused imports.

<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->



### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [ ] The title is concise and informative.
- [ ] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39011
Reported by: Tobias Diez
Reviewer(s): Dima Pasechnik
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 3, 2025
    
Related to sagemath#36801 , but this does not resolve that one. Instead:

* modify the function to respect `_repr_pretty_` just like IPython
* implement `_repr_pretty_` for `Sequence` and `PolynomialSequence`
* Add notes that `_repr_` and `cr=` and `cr_str=` of `Sequence` are
mostly unused
* Add `# need sage.groups` (automatic fix by sage-fixdoctests)

When sagemath#36801 is implemented part of this would be redundant (because
`Sequence` derives from `list`)

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [x] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.
- [x] fix doc tests
- [x] explain meaning of `cr=True` in `Sequence` constructor


### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39027
Reported by: user202729
Reviewer(s): Tobias Diez
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 3, 2025
    
<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->

Next set of formatting fixes in `manifolds`. Hopefully this time a bit
more interesting but still small enough for review ;-)

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [ ] The title is concise and informative.
- [ ] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39099
Reported by: Tobias Diez
Reviewer(s): gmou3, Tobias Diez
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 3, 2025
    
Tiny fix.


### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [x] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39127
Reported by: user202729
Reviewer(s): Martin Rubey, user202729
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 3, 2025
    
### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39157
Reported by: user202729
Reviewer(s): Tobias Diez
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 3, 2025
    
<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->

Small improvements to the Meson-based CI workflow:
- Add check that all dependencies are installed via conda (and are not
pulled-in from pypi). This copies the same check from the conda
workflow, as a preparation to delete the latter.
- In case of error, upload the meson build logs to make it easier to
investigate errors.

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [ ] The title is concise and informative.
- [ ] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39176
Reported by: Tobias Diez
Reviewer(s): Dima Pasechnik, user202729
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 3, 2025
    
<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->

Fixes sagemath#39072

Alternative to sagemath#39116.

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [x] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39179
Reported by: Kwankyu Lee
Reviewer(s): Kwankyu Lee, Marc Culler, Tobias Diez, user202729
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 3, 2025
    
<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->

preemptively as the new year is around the corner!

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39190
Reported by: Kwankyu Lee
Reviewer(s): Dima Pasechnik
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 3, 2025
    
* for some reason the proper header is needed to open the HTML file on
my machine.
* It's reported that `webbrowser.open()` doesn't work when called on a
file path, rather an URI is needed
(sagemath#38946)


### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [x] I have updated the documentation and checked the documentation
preview. (not needed)

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39193
Reported by: user202729
Reviewer(s): Martin Rubey
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 3, 2025
    
<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->

Fixes the issue raised in
sagemath/website#480 (comment)

I manually edited the release
https://github.com/sagemath/sage/releases/tag/10.5 generated by an
workflow implemented in sagemath/website#480 to
correct the changelog https://github.com/sagemath/website/blob/master/sr
c/changelogs/sage-10.5.txt, which is now in good shape. But see, for
example, https://github.com/sagemath/sage/releases/tag/10.4 that
contains all changes in betas and rcs.

This PR is for automatic generation of a release that contains only
changes from the last release.

test:
https://github.com/kwankyu/sage/releases
https://github.com/kwankyu/sage/actions/runs/12485317339/job/34844199681

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39194
Reported by: Kwankyu Lee
Reviewer(s): Soham Rane
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 3, 2025
    
<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->

With these changes it should now be possible to run doctests via pytest:
e.g. `pytest --doctest src/sage/manifolds`.

There are still a lot of errors since pytests handles a few things
differently (most notable it doesn't isolate tests from each other).
These issues will be fixed in follow-ups.

I've also moved the pytest config from `src` to the root for better
vscode integration. Added also a bit of typing information in the
doctest framework.

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [ ] The title is concise and informative.
- [ ] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39206
Reported by: Tobias Diez
Reviewer(s): Dima Pasechnik
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 3, 2025
… in multiple files

    
Discovered via pytest, which follows stricter rules when parsing
doctests.

<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->



### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [ ] The title is concise and informative.
- [ ] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39209
Reported by: Tobias Diez
Reviewer(s): Martin Rubey
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 3, 2025
    
<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->



### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [ ] The title is concise and informative.
- [ ] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39210
Reported by: Tobias Diez
Reviewer(s): Dima Pasechnik
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 3, 2025
    
Similarly to sagemath#39216, we avoid the conversion to `short_digraph` when the
input graph is an instance of `StaticSparseBackend`.

Furthermore, we use the new `PairingHeap_of_n_integers` data structure
(sagemath#39046) instead of a `priority_queue` to emulate a max-heap. This is
slightly faster this way and cleaner.


### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [x] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39217
Reported by: David Coudert
Reviewer(s): Travis Scrimshaw
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 3, 2025
Looks like the file path has changed some time earlier.

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [x] I have created tests covering the changes. (not applicable)
- [x] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->

URL: sagemath#39238
Reported by: user202729
Reviewer(s): Tobias Diez
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 5, 2025
    
By default, the Meson VS Code extension changes the paths in
`settings.json` so that C++ intellisense is working. Here we set it up
correctly and prevent further overwrites.

<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->



### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [ ] The title is concise and informative.
- [ ] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39008
Reported by: Tobias Diez
Reviewer(s): Dima Pasechnik
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 5, 2025
…hs/digraph_generators.py` (part 1)

    
We add parameter `immutable` to some generators in
`age/graphs/digraph_generators.py`.

This is straightforward for most of them, except for `RandomTournament`
where we use `getrandbits` rather than repeated calls to `random()`.
This is similar to what is done in method
`Graph(...).random_orientation()`.

This PR is motivated by discussions in sagemath#39177.

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [x] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39264
Reported by: David Coudert
Reviewer(s): Frédéric Chapoton
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 5, 2025
Fixes issue pointed out in
sagemath#38946 (comment)

### 📝 Checklist

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->

URL: sagemath#39282
Reported by: user202729
Reviewer(s): Frédéric Chapoton
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 7, 2025
    
By default, the Meson VS Code extension changes the paths in
`settings.json` so that C++ intellisense is working. Here we set it up
correctly and prevent further overwrites.

<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->



### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [ ] The title is concise and informative.
- [ ] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39008
Reported by: Tobias Diez
Reviewer(s): Dima Pasechnik
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 7, 2025
    
This fails sometimes in e.g. https://github.com/sagemath/sage/actions/ru
ns/12388661556/job/34580166155?pr=39152#step:10:9714

Marking this as random looks reasonable because one of the test above
(specifying the exact embedding) is also marked as random, and if the
embedding is random then of course the element representation in terms
of the generator `a` should also be random.


More context:

* the first `# random` is added first in https://github.com/sagemath/sag
e/commit/37fc8e88689a0197c5513161b85b8bbadd5630ab#diff-
c63508ebde0716605e6cdac05e43c8945616c2245158d30ff5ae39936ff4d9a0R1892
* then the note that `number_field_elements_from_algebraics` is OS-
dependent ("32 versus 64 bit") is removed at https://github.com/sagemath
/sage/commit/61e4df9fabf9e06a21d75eb6320ab3179bc28096 for reasons I
can't figure out. (how to find out the discussion around a commit? it
was before trac to GitHub migration)

------

Should the entry in `/.github/workflows/ci-conda-known-test-
failures.json` be removed?

```
    "sage.rings.qqbar": {
        "failed": "unreported failure on macOS seen in https://github.co
m/sagemath/sage/actions/runs/9525536510/job/26259809272?pr=37998"
    },
```

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->


------


Other failing tests:

```
TESTS:

Number fields defined by non-monic and non-integral
polynomials are supported (:issue:`252`)::

    sage: K.<a> = NumberField(2*x^4 + 6*x^2 + 1/2)
    sage: K.optimized_subfields()
    [
    (Number Field in a0 with defining polynomial x, Ring morphism:
      From: Number Field in a0 with defining polynomial x
      To:   Number Field in a with defining polynomial 2*x^4 + 6*x^2 +
1/2
      Defn: 0 |--> 0, None),
    (Number Field in a1 with defining polynomial x^2 - 2*x + 2, Ring
morphism:
      From: Number Field in a1 with defining polynomial x^2 - 2*x + 2
      To:   Number Field in a with defining polynomial 2*x^4 + 6*x^2 +
1/2
      Defn: a1 |--> a^3 + 7/2*a + 1, None),
    (Number Field in a2 with defining polynomial x^2 - 2*x + 2, Ring
morphism:
      From: Number Field in a2 with defining polynomial x^2 - 2*x + 2
      To:   Number Field in a with defining polynomial 2*x^4 + 6*x^2 +
1/2
      Defn: a2 |--> -a^3 - 7/2*a + 1, None),
    (Number Field in a3 with defining polynomial x^2 - 2, Ring morphism:
      From: Number Field in a3 with defining polynomial x^2 - 2
      To:   Number Field in a with defining polynomial 2*x^4 + 6*x^2 +
1/2
      Defn: a3 |--> a^2 + 3/2, None),
    (Number Field in a4 with defining polynomial x^2 + 1, Ring morphism:
      From: Number Field in a4 with defining polynomial x^2 + 1
      To:   Number Field in a with defining polynomial 2*x^4 + 6*x^2 +
1/2
      Defn: a4 |--> a^3 + 7/2*a, None),
    (Number Field in a5 with defining polynomial x^2 + 2, Ring morphism:
      From: Number Field in a5 with defining polynomial x^2 + 2
      To:   Number Field in a with defining polynomial 2*x^4 + 6*x^2 +
1/2
      Defn: a5 |--> 2*a^3 + 5*a, None),
    (Number Field in a6 with defining polynomial x^4 + 1, Ring morphism:
      From: Number Field in a6 with defining polynomial x^4 + 1
      To:   Number Field in a with defining polynomial 2*x^4 + 6*x^2 +
1/2
      Defn: a6 |--> a^3 + 1/2*a^2 + 5/2*a + 3/4, Ring morphism:
      From: Number Field in a with defining polynomial 2*x^4 + 6*x^2 +
1/2
      To:   Number Field in a6 with defining polynomial x^4 + 1
      Defn: a |--> -1/2*a6^3 + a6^2 - 1/2*a6)
    ]
```

I look into what determines the ordering.
It uses `_subfields_helper` which uses either `f.polred(2)` or
`f.nfsubfields(degree)`,
and there's no sorting going on.

Conclusion: marking as `random sort order` is fine. In fact it doesn't
even say which subfields
should be returned exactly, and other tests in that function are marked
as `# random` anyway,
so marking as `# random` is fine.

------

```
2024-12-18T08:35:49.0399180Z File
"src/sage/rings/number_field/number_field.py", line 8777, in
sage.rings.number_field.number_field.NumberField_absolute.subfields
2024-12-18T08:35:49.0500510Z Failed example:
2024-12-18T08:35:49.0601390Z     K.subfields()
2024-12-18T08:35:49.0707380Z Expected:
2024-12-18T08:35:49.0829700Z     [
2024-12-18T08:35:49.1013090Z     (Number Field in a0 with defining
polynomial x, Ring morphism:
2024-12-18T08:35:49.1114120Z       From: Number Field in a0 with
defining polynomial x
2024-12-18T08:35:49.1215190Z       To:   Number Field in a with defining
polynomial 2*x^4 + 6*x^2 + 1/2
2024-12-18T08:35:49.1319910Z       Defn: 0 |--> 0, None),
2024-12-18T08:35:49.1426370Z     (Number Field in a1 with defining
polynomial x^2 - 2, Ring morphism:
2024-12-18T08:35:49.1528730Z       From: Number Field in a1 with
defining polynomial x^2 - 2
2024-12-18T08:35:49.1631010Z       To:   Number Field in a with defining
polynomial 2*x^4 + 6*x^2 + 1/2
2024-12-18T08:35:49.1659980Z       Defn: a1 |--> a^2 + 3/2, None),
2024-12-18T08:35:49.1761220Z     (Number Field in a2 with defining
polynomial x^2 + 4, Ring morphism:
2024-12-18T08:35:49.1862420Z       From: Number Field in a2 with
defining polynomial x^2 + 4
2024-12-18T08:35:49.1970640Z       To:   Number Field in a with defining
polynomial 2*x^4 + 6*x^2 + 1/2
2024-12-18T08:35:49.2072220Z       Defn: a2 |--> 2*a^3 + 7*a, None),
2024-12-18T08:35:49.2173950Z     (Number Field in a3 with defining
polynomial x^2 + 2, Ring morphism:
2024-12-18T08:35:49.2275370Z       From: Number Field in a3 with
defining polynomial x^2 + 2
2024-12-18T08:35:49.2368240Z       To:   Number Field in a with defining
polynomial 2*x^4 + 6*x^2 + 1/2
2024-12-18T08:35:49.2476650Z       Defn: a3 |--> 2*a^3 + 5*a, None),
2024-12-18T08:35:49.2570570Z     (Number Field in a4 with defining
polynomial x^4 + 1, Ring morphism:
2024-12-18T08:35:49.2672100Z       From: Number Field in a4 with
defining polynomial x^4 + 1
2024-12-18T08:35:49.2774030Z       To:   Number Field in a with defining
polynomial 2*x^4 + 6*x^2 + 1/2
2024-12-18T08:35:49.2875400Z       Defn: a4 |--> a^3 + 1/2*a^2 + 5/2*a +
3/4, Ring morphism:
2024-12-18T08:35:49.2977450Z       From: Number Field in a with defining
polynomial 2*x^4 + 6*x^2 + 1/2
2024-12-18T08:35:49.3080080Z       To:   Number Field in a4 with
defining polynomial x^4 + 1
2024-12-18T08:35:49.3179890Z       Defn: a |--> -1/2*a4^3 + a4^2 -
1/2*a4)
2024-12-18T08:35:49.3281410Z     ]
2024-12-18T08:35:49.3382370Z Got:
2024-12-18T08:35:49.3483260Z     [
2024-12-18T08:35:49.3584610Z     (Number Field in a0 with defining
polynomial x, Ring morphism:
2024-12-18T08:35:49.3643330Z       From: Number Field in a0 with
defining polynomial x
2024-12-18T08:35:49.3714430Z       To:   Number Field in a with defining
polynomial 2*x^4 + 6*x^2 + 1/2
2024-12-18T08:35:49.3816090Z       Defn: 0 |--> 0, None),
2024-12-18T08:35:49.3923670Z     (Number Field in a1 with defining
polynomial x^2 - 2, Ring morphism:
2024-12-18T08:35:49.4037810Z       From: Number Field in a1 with
defining polynomial x^2 - 2
2024-12-18T08:35:49.4142230Z       To:   Number Field in a with defining
polynomial 2*x^4 + 6*x^2 + 1/2
2024-12-18T08:35:49.4289560Z       Defn: a1 |--> -a^2 - 3/2, None),
2024-12-18T08:35:49.4391330Z     (Number Field in a2 with defining
polynomial x^2 + 4, Ring morphism:
2024-12-18T08:35:49.4492300Z       From: Number Field in a2 with
defining polynomial x^2 + 4
2024-12-18T08:35:49.4602960Z       To:   Number Field in a with defining
polynomial 2*x^4 + 6*x^2 + 1/2
2024-12-18T08:35:49.4705310Z       Defn: a2 |--> -2*a^3 - 7*a, None),
2024-12-18T08:35:49.4793770Z     (Number Field in a3 with defining
polynomial x^2 + 2, Ring morphism:
2024-12-18T08:35:49.4794540Z       From: Number Field in a3 with
defining polynomial x^2 + 2
2024-12-18T08:35:49.4795030Z       To:   Number Field in a with defining
polynomial 2*x^4 + 6*x^2 + 1/2
2024-12-18T08:35:49.4795830Z       Defn: a3 |--> 2*a^3 + 5*a, None),
2024-12-18T08:35:49.4796320Z     (Number Field in a4 with defining
polynomial x^4 + 1, Ring morphism:
2024-12-18T08:35:49.4796780Z       From: Number Field in a4 with
defining polynomial x^4 + 1
2024-12-18T08:35:49.4797230Z       To:   Number Field in a with defining
polynomial 2*x^4 + 6*x^2 + 1/2
2024-12-18T08:35:49.4797760Z       Defn: a4 |--> a^3 - 1/2*a^2 + 5/2*a -
3/4, Ring morphism:
2024-12-18T08:35:49.4798180Z       From: Number Field in a with defining
polynomial 2*x^4 + 6*x^2 + 1/2
2024-12-18T08:35:49.4852940Z       To:   Number Field in a4 with
defining polynomial x^4 + 1
2024-12-18T08:35:49.4987040Z       Defn: a |--> -1/2*a4^3 - a4^2 -
1/2*a4)
2024-12-18T08:35:49.5088200Z     ]
```

Uses https://pari.math.u-
bordeaux.fr/dochtml/html/General_number_fields.html#se:nfsubfields
internally. It doesn't state any resulting sort order, so I just reorder
them (the discriminants are all distincts so it's fine).

Alternatively it looks like just doctest against the `set()` of it might
work.

------
    
URL: sagemath#39153
Reported by: user202729
Reviewer(s): Tobias Diez
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 7, 2025
    
<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->

In line with Spec 0, we drop Python 3.9 and 3.10 support (in this PR
only for conda). Instead Python 3.11 and 3.12 is used for the CI.

(Python 3.13 still needs a few package updates in the conda universe
sagemath#39163)

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [ ] The title is concise and informative.
- [ ] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39164
Reported by: Tobias Diez
Reviewer(s): Dima Pasechnik
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 7, 2025
    
Alternative to sagemath#39181 .

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [x] I have created tests covering the changes. (no behavior change)
- [x] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39184
Reported by: user202729
Reviewer(s):
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 7, 2025
…hs/digraph_generators.py` (part 1)

    
We add parameter `immutable` to some generators in
`age/graphs/digraph_generators.py`.

This is straightforward for most of them, except for `RandomTournament`
where we use `getrandbits` rather than repeated calls to `random()`.
This is similar to what is done in method
`Graph(...).random_orientation()`.

This PR is motivated by discussions in sagemath#39177.

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [x] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39264
Reported by: David Coudert
Reviewer(s): Frédéric Chapoton
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 7, 2025
…Spec 0

    
<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->

Following https://scientific-python.org/specs/spec-0000/, we update the
version requirements of a few dependencies so that sage code can use new
features form these libraries.


### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [ ] The title is concise and informative.
- [ ] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39268
Reported by: Tobias Diez
Reviewer(s): Dima Pasechnik
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 7, 2025
    
Fixes issue pointed out in
sagemath#38946 (comment)

### 📝 Checklist

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39282
Reported by: user202729
Reviewer(s): Frédéric Chapoton
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 7, 2025
    
<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->

As suggested at
sagemath#39206 (comment).

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [ ] The title is concise and informative.
- [ ] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39284
Reported by: Tobias Diez
Reviewer(s): Dima Pasechnik
vbraun pushed a commit to vbraun/sage that referenced this issue Jan 7, 2025
…aracters

    
<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->

The new release creation workflow introduced by
sagemath#39194 failed for the latest
release:

https://github.com/sagemath/sage/actions/runs/12612595224/job/3514974517
9

with the message "Problems parsing JSON". See the "Create release" step.
Reported by passagemath/passagemath#638

We fix it by escaping special characters in `release_notes` for json
input.

test: https://github.com/kwankyu/sage/releases/tag/10.7.beta3
test workflow run:
https://github.com/kwankyu/sage/actions/runs/12620257460/job/35165981375

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [x] The title is concise and informative.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#39288
Reported by: Kwankyu Lee
Reviewer(s): Soham Rane
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants