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
use weakref for PolyBoRi #3284
Comments
comment:2
Hello again, Best regards, |
comment:3
My guess is that we somewhere forget to set the global ring maybe? |
Attachment: pbori_weakref.patch.gz this patch is supposed to work |
This comment has been minimized.
This comment has been minimized.
Changed keywords from PolyBoRi, segfault to PolyBoRi |
comment:5
Please review the updated patch which fixes the doctest failure. |
comment:6
I don't see why the changes to pbori.pyx other than the addition of the R._pbring.activate() at line 4131 are necessary. In |
comment:7
True, it is unrelated to this particular weakref patch. I mixed up two things. The renaming only cleans up since vars is a built-in identifier and it is considered bad practice to use it like we used to use it. |
Changed keywords from PolyBoRi to PolyBoRi, editor_malb |
BooleanPolynomialRing user friendly names |
comment:9
Attachment: trac3284_BooleanPolynomialRing_normalize_names.patch.gz
I give malb's patch (followed by mine) a positive review. Someone should review my patch, especially the change to |
comment:10
Burcin's patch looks good and passes doctests. |
comment:11
All doctests pass with the patch applied and valgrind gives pbori.pyx a clean bill of health. Cheers, Michael |
comment:12
Merged in Sage 3.0.4.alpha1 |
This patch makes sure only one
BooleanPolynomialRing
per parameter set is created by returning a reference to a prior created object if there is such a reference.CC: @burcin @sagetrac-PolyBoRi
Component: commutative algebra
Keywords: PolyBoRi, editor_malb
Issue created by migration from https://trac.sagemath.org/ticket/3284
The text was updated successfully, but these errors were encountered: