Opened 3 years ago
Last modified 6 months ago
#28696 new defect
qsieve with time=True doesn't work
| Reported by: | embray | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | sage-pending |
| Component: | porting: Cygwin | Keywords: | qsieve cygwin time |
| Cc: | Merged in: | ||
| Authors: | Reviewers: | ||
| Report Upstream: | N/A | Work issues: | |
| Branch: | Commit: | ||
| Dependencies: | Stopgaps: |
GitHub link to the corresponding issue
Description
When running something like qsieve(n, time=True), for some reason it uses the built-in time command in the shell to do this (is there really any advantage in that?)
However, on Cygwin, there is not a time program by default; it is a bash shell built-in, and there is no wrapper executable for it, so trying to run time with Popen fails as reported here: https://ask.sagemath.org/question/48549/qsieve-error/
A workaround would be to just use timeit, like
sage: timeit('qsieve(n)', repeat=1, number=1)
Change History (8)
comment:1 Changed 3 years ago by
| Milestone: | sage-9.0 → sage-9.1 |
|---|
comment:2 Changed 3 years ago by
| Milestone: | sage-9.1 → sage-9.2 |
|---|
Moving tickets to milestone sage-9.2 based on a review of last modification date, branch status, and severity.
comment:3 Changed 2 years ago by
| Milestone: | sage-9.2 → sage-9.3 |
|---|
comment:4 Changed 21 months ago by
| Milestone: | sage-9.3 → sage-9.4 |
|---|
Moving to 9.4, as 9.3 has been released.
comment:5 Changed 18 months ago by
| Milestone: | sage-9.4 → sage-9.5 |
|---|
comment:6 Changed 14 months ago by
| Milestone: | sage-9.5 → sage-9.6 |
|---|
comment:7 Changed 9 months ago by
| Milestone: | sage-9.6 → sage-9.7 |
|---|
comment:8 Changed 6 months ago by
| Milestone: | sage-9.7 → sage-pending |
|---|
Note: See
TracTickets for help on using
tickets.
Ticket retargeted after milestone closed