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
Inherit __richcmp__ and __cmp__ in subclasses of Element #18329
Comments
Branch: u/jdemeyer/inherit_richcompare |
Commit: |
Last 10 new commits:
|
Changed branch from u/jdemeyer/inherit_richcompare to none |
This comment has been minimized.
This comment has been minimized.
Changed commit from |
Branch: u/jdemeyer/ticket/18329 |
New commits:
|
Commit: |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:10
Almost there :-)
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:35
Ok, that is good news, I was kind of afraid that this patch was not so useful :) Do you plan on opening a follow-up ticket to remove all the now superfluous boilerplate code? I guess my only concern left is about the comments in |
comment:36
Replying to @jpflori:
As far as I know, there is not. There is some documentation in I do plan to write documentation in #18306, but I haven't gotten around to actually do it.
I'll have a look. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Reviewer: Jean-Pierre Flori |
comment:38
Thanks! |
comment:39
Replying to @jpflori:
Since this would be ticket with a lot of potential conflicts, it's best if the author and potential reviewer agree in advance that such a thing be a good idea and to try to get that ticket merged quickly after a new beta comes out. Can you do that? |
comment:40
|
comment:41
Any clue why the extension changed from |
comment:42
I think its because |
comment:43
I cannot reproduce this problem... suggestions? |
comment:44
Are you really sure that this ticket is causing that problem? |
comment:45
Cannot reproduce on |
comment:46
Can we still replace it with |
Branch pushed to git repo; I updated commit sha1. New commits:
|
New commits:
|
Changed branch from u/jdemeyer/ticket/18329 to |
Changed commit from |
Use the
__typeinit__
mechanism introduced by #18330 to inherit__cmp__
and__richcmp__
even if those would not be inherited by default.Upstream patch added: cython/cython#383
Upstream: Fixed upstream, but not in a stable release.
CC: @jpflori
Component: coercion
Author: Jeroen Demeyer
Branch:
f6058e7
Reviewer: Jean-Pierre Flori
Issue created by migration from https://trac.sagemath.org/ticket/18329
The text was updated successfully, but these errors were encountered: