Ticket #4058 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

[with patch, positive review] move integer ring to the new coercion model

Reported by: robertwb Owned by: robertwb
Priority: major Milestone: sage-3.1.3
Component: coercion Keywords:
Cc: AlexGhitza, malb Author(s):
Report Upstream: Reviewer(s):
Merged in: Work issues:

Description

A couple of bugfixes are included as well.

Attachments

4058-integer-coerce.patch Download (38.6 KB) - added by robertwb 2 years ago.
4058-integer-coerce.2.patch Download (38.5 KB) - added by robertwb 2 years ago.

Change History

Changed 2 years ago by robertwb

  Changed 2 years ago by AlexGhitza

I'm getting an error trying to apply this patch to a fresh 3.1.2:

patching file sage/interfaces/expect.py
Hunk #1 FAILED at 1385
1 out of 1 hunk FAILED -- saving rejects to file sage/interfaces/expect.py.rej
patch failed, unable to continue (try -v)
patch failed, rejects left in working dir

  Changed 2 years ago by robertwb

I'll rebase this as soon as I get 3.1.2.

  Changed 2 years ago by AlexGhitza

  • cc AlexGhitza added

Changed 2 years ago by robertwb

  Changed 2 years ago by robertwb

Refreshed the patch so it applies cleanly to 3.1.2.

  Changed 2 years ago by mhansen

  • summary changed from [with patch, needs review] move integer ring to the new coercion model to [with patch, positive review] move integer ring to the new coercion model

Looks good to me.

  Changed 2 years ago by mabshoff

  • cc malb added

One thing I notice with this patch is that sr.py now takes around 650 seconds instead of 450 or so:

sage -t -long devel/sage/sage/crypto/mq/sr.py
         [655.1 s]

I am still merging the patch, but can we get this issue fixed next?

Cheers,

Michael

  Changed 2 years ago by mabshoff

  • status changed from new to closed
  • resolution set to fixed

Merged 4058-integer-coerce.2.patch in Sage 3.1.3.alpha1

  Changed 2 years ago by robertwb

I will certainly look into that.

follow-up: ↓ 11   Changed 2 years ago by robertwb

Interestingly enough, on my machine sage -t sage/crypto/mq/sr.py, so it is just the (single) long doctest that provides the slowdown.

  Changed 2 years ago by robertwb

See #4186 for a fix.

in reply to: ↑ 9   Changed 2 years ago by mabshoff

Replying to robertwb:

Interestingly enough, on my machine sage -t sage/crypto/mq/sr.py, so it is just the (single) long doctest that provides the slowdown.

Yeah, in that doctest we do some wacky coercion into some mv polynomial ring with a couple thousand variables, so this is really an interesting test case. This was first discussed at SD6 in Bristol, so it just shows how much the coercion re-re-write has been an interesting road :)

Cheers,

Michael

Note: See TracTickets for help on using tickets.