[sage-devel] pari-jupyter 1.4.3 release candidate

[Matthias Koeppe]

- https://pypi.org/project/pari-jupyter/1.4.3rc1/
- I've added simple CODE_OF_CONDUCT and CONTRIBUTING files that just point 
to the main sagemath repository
- using WIP sage-project-cookiecutter to simplify maintenance 
https://github.com/sagemath/sage/pull/37541

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e822f186-6504-4516-9940-d03398f270b9n%40googlegroups.com.

[sage-devel] pplpy 0.8.10 release candidate

[Matthias Koeppe]

I have prepared a release candidate for pplpy 0.8.10
- https://pypi.org/project/pplpy/0.8.10rc2/
- I've added simple CODE_OF_CONDUCT and CONTRIBUTING files that just point 
to the main sagemath repository
- using WIP sage-project-cookiecutter to simplify maintenance 
https://github.com/sagemath/sage/pull/37541
- needs testing: the new binary wheels (built using Sage distribution + 
cibuildwheels for Linux and macOS, including arm64) 
- https://pypi.org/project/pplpy/0.8.10rc2/#files
- try with "pip install --pre pplpy"

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/dad25da4-60a6-4ae8-a617-712b9445fe2an%40googlegroups.com.

Re: [sage-devel] Re: VOTE: Use "CI Fix" label for merging into continuous integration runs

[David Roe]

This vote has passed, and I've added a "CI Fix" label
 on github.  I am
not going to have time to implement changes to our CI infrastructure in the
near future, but others are welcome to do so.
David

On Sun, Mar 10, 2024 at 1:37 PM seb@gmail.com 
wrote:

> +1
>
> Eric Gourgoulhon schrieb am Sonntag, 10. März 2024 um 16:58:42 UTC+1:
>
>> +1
>>
>> Eric.
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/d35c59ad-b5a6-4fb7-9a2f-8d0adc238ce3n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAChs6_kLCfTTP6qU4p07wjJ_suZbztSvqNfQsqeX%2BDDhSzycoA%40mail.gmail.com.

Re: [sage-devel] Re: Vote: Sage Code of Conduct

[David Roe]

On Mon, Mar 18, 2024 at 11:10 AM Dima Pasechnik  wrote:

> It's very important to note that with multiwinner approval voting, merely
> counting the votes per candidate and picking the top ones can lead to
> rather unfair results
> (unlike in the single winner case).
>
> For instance, if we elect k=3 candidates out of 6, say, $a,b,c,d,e,f$, and
> out of N=19 people, 10 vote for $a,b,c$, and 9 - for $d,e,f$, then, with
> approval voting, $a,b,c$ get elected (as $a,b,c$, get 10 votes each, more
> than $d,e,f$), and almost half the voters, 9 out of 10, get no
> representation of their views.
> This is obviously bad - in such a case a fair outcome would be something
> like $a,b,d$. Here "fair" has to be quantified, of course.
> I've posted some details (and pointed at some solutions) on this here:
> https://github.com/sagemath/sage/pull/37501#issuecomment-2004121053
>
> It would be interesting to get the anonymised returned ballots and see if
> we did well on this occasion.
> As well, adjustments ought to be made along the lines outlined above.
>

The committee has agreed to release anonymized voting records, since the
benefit gained for picking a better system for future votes outweighs the
privacy risk (we've anonymized both voters and candidates).  As I explained
here ,
if we had stuck with 5 people on the committee then different system would
have had different results, but after extending to 6 based on the
approval-voting tie there was broad agreement: Approval Voting,
Proportional Approval Voting, Phragmén's sequential rule, Maximin Support
and Equal Shares all selected the current committee; only Minimax approval
voting had a different result.

The anonymized votes are here
,
in case anyone wants to do further analysis.
David

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAChs6_km71CEnaVUQX4T5mkGz6zMEZKLjfuXW3fsd1w50wNFSw%40mail.gmail.com.

[sage-devel] Re: UniqueRepresentation MRO Question

[Travis Scrimshaw]

Dear Enrique,
   No, that would just duplicate functionality and make things more 
complicated.

To Cython and/or Python experts,
   It would be great if someone could give some comments about this. This 
feels like a very natural thing to do, but it might lead to a very subtle 
breakage in the wild. If there is anything additional I can provide, please 
just ask.

Thank you,
Travis

On Monday, March 18, 2024 at 1:15:18 AM UTC+9 enriqu...@gmail.com wrote:

> Is there any sense to define a new class of UniqueRepresentation with the 
> same characteristics and  other name with the switch of order?  
>
> El miércoles, 13 de marzo de 2024 a las 16:58:49 UTC+1, Travis Scrimshaw 
> escribió:
>
>> Hi everyone,
>>On https://github.com/sagemath/sage/pull/37128, we find it useful to 
>> swap the order of the base classes for UniqueRepresentation. Thus, it 
>> becomes
>>
>> class UniqueRepresentation(WithEqualityById, CachedRepresentation):
>>
>> I believe this is very reasonable since we want to have objects' 
>> (typically parents, but not limited to them) comparison and hashing be 
>> first in the MRO. In particular, this is important if we have the following 
>> setup:
>>
>> class Foo(CachedRepresentation):
>> pass
>>
>> class Bar(UniqueRepresentation, Foo):
>> pass
>>
>> That way Bar gets the main benefits of being a UR (fast equality and 
>> hashing). With the current way, there is no way (that I know) to simply 
>> have the corresponding methods at the Cython level (at best, there is a 
>> Python redirect that has to be manually implemented) since WithEqualityById 
>> is a Cython cdef class.
>>
>> However, we then have a problem with unpickling, but I suspect it is a 
>> bigger issue. From combinat/root_system/cartan_type.py, the last line fails 
>> with an incompatible class order:
>>
>> sage: pg_CartanType_simple_finite = 
>> unpickle_global('sage.combinat.root_system.cartan_type', 
>> 'CartanType_simple_finite')
>> sage: si1 = unpickle_newobj(pg_CartanType_simple_finite, ())
>> sage: from sage.misc.fpickle import unpickleModule
>> sage: pg_make_integer = unpickle_global('sage.rings.integer', 
>> 'make_integer')
>> sage: si2 = pg_make_integer('4')
>> sage: unpickle_build(si1, 
>> {'tools':unpickleModule('sage.combinat.root_system.type_A'), 't':['A', 
>> si2], 'letter':'A', 'n':si2})
>>
>> Mainly, the last line does a self.__class__ = UR.__class__, where UR is 
>> an instance of a UniqueRepresentation. Granted, this is a very old pickle, 
>> but I am worried it isn't a problem with this specific pickle.
>>
>> This is beyond my knowledge of Cython. Any thoughts or advice about this 
>> issue would be appreciated.
>>
>> Thank you,
>> Travis
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0966e7ed-6875-4e4a-89bc-eb043f3d9efbn%40googlegroups.com.