Yes, I already installed the package python3-pip
Il giorno lunedì 7 aprile 2025 alle 02:49:00 UTC+2 marc@gmail.com ha
scritto:
> Did you install the package python3-pip? That is separate from the
> python3 package on Unbuntu 24.04.
>
> - Marc
>
> On Sunday, April 6, 2025 at 8:38:25 AM UTC-
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 of echo $PATH:
/usr/sbin/:/sbin/:/bin/:/usr/lib/wsl/lib/
Il giorno domenica 6 aprile 2025 alle 21:39:08 UTC+2 dim
On Sun, Apr 6, 2025 at 6:07 PM Marc Culler wrote:
>
> This is surely not the place for a long technical discussion of the problems
> that have to be solved to produce the macOS app. Let me just mention one
> item at the tip of the iceberg, ignoring, for example, how we go about
> making sage
Did you install the package python3-pip? That is separate from the python3
package on Unbuntu 24.04.
- Marc
On Sunday, April 6, 2025 at 8:38:25 AM UTC-5 leon.va...@gmail.com wrote:
> I already installed it, as python3, and it is Python 3.12. Actually I
> already installed python3-setuptools a
This is surely not the place for a long technical discussion of the
problems that have to be solved to produce the macOS app. Let me just
mention one item at the tip of the iceberg, ignoring, for example, how we
go about making sage relocatable and self-contained, with no symlinks or
rpaths
Nils,
I think that your assessment of the situation is accurate, and that your
proposed solution:
> 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 i
Are you not mixing up Python installed in Windows with Python installed in WSL?
In WSL terminal, what is the output of
python3
command?
What is the output of
echo $PATH
command?
On 6 April 2025 04:52:03 GMT-05:00, "Léon Vaia"
wrote:
>I already installed it, as python3, and it is
On Sun, Apr 6, 2025 at 11:40 AM Dima Pasechnik wrote:
> On 6 April 2025 11:41:21 GMT-05:00, Nils Bruin wrote:
> >It looks to me that there are two points of view here.
> >
> >1) Having sagemath detect python version requirements and build its own if
> >not acceptable version is found leads to inc
On 6 April 2025 11:41:21 GMT-05:00, Nils Bruin wrote:
>It looks to me that there are two points of view here.
>
>1) Having sagemath detect python version requirements and build its own if
>not acceptable version is found leads to increased support requests.
I repeat - it is not only increased
It looks to me that there are two points of view here.
1) Having sagemath detect python version requirements and build its own if
not acceptable version is found leads to increased support requests.
2) The macos app should package its own python and that is conveniently
done by letting sagemath
I already installed it, as python3, and it is Python 3.12. Actually I
already installed python3-setuptools as well. Why is it still building it
from source?
Il giorno sabato 5 aprile 2025 alle 19:58:30 UTC+2 dim...@gmail.com ha
scritto:
> Oh, this is yet another example of the harm caused by t
export PATH=/opt/homebrew/bin:$PATH # on arm64
(on Intel, do
export PATH=/usr/local/bin:$PATH
instead)
source .homebrew-build-env
./configure
should work
On 5 April 2025 12:42:09 GMT-05:00, Tagir Eminov
wrote:
>i did:
>source .homebrew-build-env
>./config (tried with python modules flag)
Hi all! I saw Tobias mentioning `uv` on another sage-devel thread. I looked into
Sage's commits and saw that we have switched to using `uv` in some of our
workflows as of two weeks ago also by Tobias. Is there any future roadplan for
using it more in Sage? Or do we have to wait for them to support
13 matches
Mail list logo
