[sage-devel] Re: maxima-to-sr exception in `sum(1/(5*n)-1/(5*n+1),n,2,oo)`

[dmo...@deductivepress.ca]

Thanks for reporting the bug. I opened issue 
#36770 
 to track this, and provided 
a diagnosis there.

On Saturday, November 25, 2023 at 7:30:06 AM UTC-7 Georgi Guninski wrote:

> ```
> n=var('n')
> su1=sum(1/(5*n)-1/(5*n+1),n,2,oo);su1
> ```
> RuntimeError: Encountered operator mismatch in maxima-to-sr translation
>

-- 
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/d4a4f77f-6f3d-4e5c-894d-0471f8fd961bn%40googlegroups.com.

Re: [sage-devel] Removing Cygwin support

[Dima Pasechnik]

On 25 November 2023 12:55:54 GMT, Michael Orlitzky  wrote:
>We dropped Cygwin support in September 2022,
>
>  https://github.com/sagemath/sage/wiki/Sage-9.7-Release-Tour
>
>but that was mainly a documentation change reflecting the fact that
>Cygwin support had bit-rotted.
>
>Anyone could have fixed it at that point -- or in the meantime -- but
>no one has done so. I think it's time to admit that Cygwin is a dead
>platform for us. WSL is a much easier replacement these days if your
>goal is to get Sage running on Windows.
>
>The issue was made relevant again by PR #36129 which reintroduces the
>psutil package as standard. The meat of psutil is platform-specific C
>code that does not work on Cygwin, and it's not something we can
>realistically fix.
>
>If it's never coming back, I'd like to start removing the old Cygwin
>workarounds from sage. This is your heads up in case there are still
>users out there.

Please proceed.
I'm pretty certain Cygwin won't be around any more in few years.
It was a serious waste of resources to have it supported in the 1st place 
(well, Windows support was a part of our Horizon 2020 grant...)



>
>

-- 
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/C41B754D-B63B-4B2B-A501-913C0948D1E0%40gmail.com.

[sage-devel] maxima-to-sr exception in `sum(1/(5*n)-1/(5*n+1),n,2,oo)`

[Georgi Guninski]

```
n=var('n')
su1=sum(1/(5*n)-1/(5*n+1),n,2,oo);su1
```
RuntimeError: Encountered operator mismatch in maxima-to-sr translation

-- 
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/CAGUWgD-OwxWZyhiF3OWBG%3Dm%3Dy0RHLjDGdSo1c3WwR8D%2Bk57OhA%40mail.gmail.com.

[sage-devel] Removing Cygwin support

[Michael Orlitzky]

We dropped Cygwin support in September 2022,

  https://github.com/sagemath/sage/wiki/Sage-9.7-Release-Tour

but that was mainly a documentation change reflecting the fact that
Cygwin support had bit-rotted.

Anyone could have fixed it at that point -- or in the meantime -- but
no one has done so. I think it's time to admit that Cygwin is a dead
platform for us. WSL is a much easier replacement these days if your
goal is to get Sage running on Windows.

The issue was made relevant again by PR #36129 which reintroduces the
psutil package as standard. The meat of psutil is platform-specific C
code that does not work on Cygwin, and it's not something we can
realistically fix.

If it's never coming back, I'd like to start removing the old Cygwin
workarounds from sage. This is your heads up in case there are still
users out there.


-- 
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/6e797b162a0501b3646be9bfca2e0fe3ed7ab6b6.camel%40orlitzky.com.

[sage-devel] Re: Policy for disputed PRs: discussion

[Kwankyu Lee]

I agree that we need a policy for disputed PRs.

Such a policy should not operate in a way to condemn those raising 
objections to the PR since we want to keep kind, productive, caring 
atmosphere as Matthias put it. The policy should be clear and operate 
semi-automatically. So I suggest the following detail:

(1) When a PR becomes a disputed PR? A PR becomes a disputed PR when one 
reviewer adds "positive review" label, another reviewer removes it, and the 
author does not plan to work more on the PR according to the reviewer 
objections.

(2) How do we count approvers and disapprovers for a disputed PR: A 
reviewer becomes an approver (who is in favor of the PR) when he/she sets 
"Approve" in the github review system. A reviewer becomes a disapprover 
(who objects the PR) when he/she sets "Request changes" in the github 
review system.

Kwankyu

-- 
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/b2acbda8-c0bc-4fe6-b9d4-a6ee719951aan%40googlegroups.com.