Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

On Mon, Apr 7, 2025 at 5:12 PM Marc Culler wrote: > > > > On Mon, Apr 7, 2025 at 3:25 PM Dima Pasechnik wrote: >> >> >> It's not standard - no-one nowadays builds Sage's Python, not even CI is >> doing this. >> >> This is the point I already made. >> You are the sole users of this semi-broken fea

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

It is likely the case, but this is exactly my point - we don't want to spend our and other people time on solving a problem no other python package out there is doing - building Python from source. I am all ears as far as needs of building macOS app is concerned, I am willing to spend my time o

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

On 15:11 Sun 06 Apr 2025, Marc Culler wrote: We could just have a configure flag "--install_own_python" to allow the prerequisite requirement to be fulfilled by building the python spkg; an option that would by default be off. would be ideal for the Sage_macOS project. I would be very happy wi

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

As this discussion tries to wander off into a new discussion about the uv project, I will attempt to bring it back on topic. The point is this: Currently, to build the macOS binary, we first build sage in a completely standard way. The only customization we need to do is to set up the configure

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

On Mon, Apr 7, 2025 at 10:03 AM Dima Pasechnik wrote: > We do see similar problems on Linux being run in WSL. It's probably due to > WSL defaulting to an old Ubuntu version, on which you need to jump extra > hoops to install modern Python. > The most recent such issue

Re: [sage-devel] Error running the pipinst script for setuptools-73.0.1.

Could you please post the top-level config.log On 7 April 2025 01:19:21 GMT-05:00, "Léon Vaia" wrote: > >Output of python3 on wsl terminal: >Python 3.12.3 (main, Feb 4 2025, 14:48:35) [GCC 13.3.0] on linux >Type "help", "copyright", "credits" or "license" for more information. > >Output

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

On 7 April 2025 07:48:37 GMT-05:00, Nathan Dunfield wrote: > > >1) Having sagemath detect python version requirements and build its own if >not acceptable version is found leads to increased support requests. > >[...] > >It seems to me that for 1) it isn't so important if python occurs as an

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

> I believe that Homebrew wouldn't work because of the issue with rpaths that > Marc hints at earlier in his message -- in particular the paths are baked in > as /opt/homebrew/* and will not survive relocation. The "uv" installer can > install in varying locations, but I'm not sure the result i

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

On Monday, April 7, 2025 at 1:19:45 AM UTC-5 Dima wrote: Homebrew, uv, etc provide single-arch Python3 just fine. I believe that Homebrew wouldn't work because of the issue with rpaths that Marc hints at earlier in his message -- in particular the paths are baked in as /opt/homebrew/* and will

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

1) Having sagemath detect python version requirements and build its own if not acceptable version is found leads to increased support requests. [...] It seems to me that for 1) it isn't so important if python occurs as an spkg or not -- the main issue there would be resolved if the build pro