Re: [sage-devel] Proposal: Policy for standard packages from binary wheelsall

2024-08-14 Thread Kwankyu Lee
The installation guide does not tell me where I can download sage-10.4.tar.gz that contains upstream/ directory. Where is it? See https://doc.sagemath.org/html/en/installation/source.html#installation-steps Yes, there it is though quite buried among many files. Thanks. You may recall tha

Re: [sage-devel] Proposal: Policy for standard packages from binary wheelsall

2024-08-14 Thread Matthias Koeppe
On Wednesday, August 14, 2024 at 3:08:39 PM UTC-7 Kwankyu Lee wrote: On Thursday, August 15, 2024 at 4:11:50 AM UTC+9 Matthias Koeppe wrote: On the other hand, the "sage-10.4.tar.gz" tarball that is built by the Release Manager and put on the Sage mirrors (as well as the "sage-10.4.tar.gz" tarb

[sage-devel] Re: message marked as off topic

2024-08-14 Thread Kwankyu Lee
These actions on our github site: A1 marking a comment as off topic on a PR A2 blocking someone from a PR A3 blocking someone totally from the github project (that is, expelling someone from our project) A4 modifying a comment by someone else (including modifying the PR description) A5 using par

Re: [sage-devel] Proposal: Policy for standard packages from binary wheelsall

2024-08-14 Thread Kwankyu Lee
On Thursday, August 15, 2024 at 4:11:50 AM UTC+9 Matthias Koeppe wrote: On the other hand, the "sage-10.4.tar.gz" tarball that is built by the Release Manager and put on the Sage mirrors (as well as the "sage-10.4.tar.gz" tarball that is built using the same procedure and put on GitHub Release

Re: [sage-devel] Proposal: Policy for standard packages from binary wheelsall

2024-08-14 Thread Matthias Koeppe
On the other hand, the "sage-10.4.tar.gz" tarball that is built by the Release Manager and put on the Sage mirrors (as well as the "sage-10.4.tar.gz" tarball that is built using the same procedure and put on GitHub Releases - https://github.com/sagemath/sage/releases/tag/10.4) does contain an u

Re: [sage-devel] Proposal: Policy for standard packages from binary wheelsall

2024-08-14 Thread Matthias Koeppe
On Wednesday, August 14, 2024 at 7:50:52 AM UTC-7 Kwankyu Lee wrote: There are multiple "tarballs" (actually wheel files) listed in checksums.ini and uploaded/downloaded to/from GitHub Releases and the Sage mirrors Together they cover the supported platforms. Thanks. I confess that I misunde

Re: [sage-devel] Proposal: Policy for standard packages from binary wheelsall

2024-08-14 Thread Kwankyu Lee
Yes. There are multiple "tarballs" (actually wheel files) listed in checksums.ini and uploaded/downloaded to/from GitHub Releases and the Sage mirrors Together they cover the supported platforms. Thanks. I confess that I misunderstood things about installing sage from source. I thought, fo

Re: [sage-devel] Re: Proposal: Policy for standard packages from binary wheels

2024-08-14 Thread Matthias Koeppe
Nathan explained it correctly. On Tuesday, August 6, 2024 at 1:45:21 PM UTC-7 Nathan Dunfield wrote: > Dima, > > As I understand it, while both proposals result in binary wheels being > pulled off PyPI for certain standard packages, they differ in that: > > a) The current proposal requires the v

Re: [sage-devel] Proposal: Policy for standard packages from binary wheelsall

2024-08-14 Thread Matthias Koeppe
On Tuesday, August 13, 2024 at 4:36:18 PM UTC-7 Kwankyu Lee wrote: > Does this [platform-dependent standard package] mean that there will be different sage tarballs for supported platforms? Yes. There are multiple "tarballs" (actually wheel files) listed in checksums.ini and uploaded/downloade

Re: [sage-devel] Re: hyperbolic_polygon bug

2024-08-14 Thread Vincent Delecroix
Let me advertize that sage-flatsurf (https://github.com/flatsurf/sage-flatsurf) has an implementation of the hyperbolic plane with exact coordinates The following code ``` from flatsurf import HyperbolicPlane H = HyperbolicPlane(AA) z0 = H.point(2*AA(2).sqrt()/3 - 1, 4/6, model='half_plane') z1 =

[sage-devel] Re: message marked as off topic

2024-08-14 Thread 'Martin R' via sage-devel
Concerning technology: I was not notified by github that my comment was marked off topic. Concerning collaboration: I think that no matter who (e.g. a single person or the community angels) marks a comment as off topic, or removes or adds a disputed label, or modifies the description of a pull