__cmp__ is gone in Python 3 see [1]. The way to implement comparisons
wil be through the various __lt__, __eq__, etc. There is already a
ticket opened for dealing with that in #16537. It would be better to
think about a solution that takes this into account. I do not know the
Cython way.
There is
If you are at all interested in attending a fully funded Sage Days
during the next few months, please fill out this form. Thanks, William
There is a lot of funding (for US people) for several Sage Days
sometime between now and September 2015. All this funding vanishes on
Sept 1, 2015.
I've invi
Then lets put a stopgap when Sage starts, since Sage has many known bugs
but we don't have good ways to check against those inputs (which is worse
because the vast majority of these aren't even documented). It's dangerous
to use Sage.
Yes I know I'm being slightly ridiculous, but it does hol
On 2015-03-05, Nathann Cohen wrote:
> Hello everybody,
>
> I write this email because I would like your opinion on a ticket that is
> being
> written.
>
> - In #17637 [1], a stopgap (warning) was added in `IntegerListsLex`, to warn
> users against wrong results returned by this function.
>
> - I
You can open the ticket. The patch worked and all the tests for flint
passed. Here's what I did in order to test it:
tar xvfz sage-6.5.tar.gz
cd sage-6.5
# MANUALLY PATCHED Makefile.in in upstream/flint-2.4.4.tar.gz
# MANUALLY PATCHED build/pkgs/flint/checksums.ini to reflect the change
Thanks, Thierry!
I already found an alternative way to do what I wanted, using
from scipy.stats.mstats import mquantiles
However, I thought that the examples in the documentation should work in
the sage notebook without fundamentally changing the syntax, and hence I
considered this a bug. Othe
On 2015-03-05 09:58, Nathann Cohen wrote:
Could you please share your opinion on whether we should keep or remove this
stopgap?
Normally I would say: just write a few lines of code to check the input
conditions and be done with it. That would obviously be the best solution.
Since this seems to
On 2015-03-04 22:37, Travis Scrimshaw wrote:
Would it also be possible to check if (python) rich comparisons are
implemented and use those first before falling back to _cmp_, or having
the default try to call the rich comparisons?
Possible: maybe. But checking for Python-level stuff in Cython
Hello everybody,
I write this email because I would like your opinion on a ticket that is
being
written.
- In #17637 [1], a stopgap (warning) was added in `IntegerListsLex`, to warn
users against wrong results returned by this function.
- In #17898 [2], this stopgap is being removed, under the
