Re: Forcing python39 on M1

2021-03-13 Thread Todd Doucet
Without intending to criticize any individual effort, I nevertheless respectfully suggest that something is less than ideal from a design & system standpoint, and I offer this because I think macports generally tries to get these high-level decisions architectural decisions right. I think at co

Re: Forcing python39 on M1

2021-03-13 Thread petr.2006
#project.tickets to report a bug. Error: Processing of port gimp-app failed Petr __ > Od: "Rainer Müller" > Komu: "Peter West" , "MacPorts Users" > > Datum: 13.03.2021 14:33 > Předmět: Re: F

Re: Forcing python39 on M1

2021-03-13 Thread Ryan Schmidt
On Mar 13, 2021, at 10:38, Todd Doucet wrote: > At some point I might try to determine whether I can get a useful python3 > setup using Macports, but it is time-consuming and the status pages do not > help, as the comments indicate. > > When I tried a few weeks ago, I could install either py38

Re: Forcing python39 on M1

2021-03-13 Thread Todd Doucet
To be super-clear, the problems I am describing all relate to the M1 version of the python libraries. > At some point I might try to determine whether I can get a useful python3 > setup using Macports, but it is time-consuming and the status pages do not > help, as the comments indicate. > > W

Re: Forcing python39 on M1

2021-03-13 Thread Todd Doucet
At some point I might try to determine whether I can get a useful python3 setup using Macports, but it is time-consuming and the status pages do not help, as the comments indicate. When I tried a few weeks ago, I could install either py38 or py39, and that is fine if I want to write "hello worl

Re: Forcing python39 on M1

2021-03-13 Thread Dave Allured - NOAA Affiliate via macports-users
*Sigh*. The ports.macports.org site has not been getting updates since Feb 20. See recent threads. Yes, this is *usually* reliable. Not this month. On Sat, Mar 13, 2021 at 8:23 AM Ken Cunningham < ken.cunningham.web...@gmail.com> wrote: > > Having heard that python39 is the only one (so far)

Re: Forcing python39 on M1

2021-03-13 Thread Ken Cunningham
> Having heard that python39 is the only one (so far) to compile natively on > M1, I’m trying to force the python ports I use to python39 Hello Peter, FYI, an arm64 version of python38 appears to be available: http://packages.macports.org/python38/python38-3.8.8_0.darwin_20.arm64.tbz2 and is “

Re: Forcing python39 on M1

2021-03-13 Thread Peter West
Thanks Rainer. Pardon my ignorance, but could you elaborate on “bump the port version” please? I assume that will have ramifications for all the dependents as well. Peter — p...@ehealth.id.au “Two men went up into the temple to pray, one a Pharisee and the other a tax collector.” > On 13 Mar 2

Re: Forcing python39 on M1

2021-03-13 Thread Rainer Müller
On 12/03/2021 12.16, Peter West wrote: >> I ran intoa brick wall with gexiv2, which was because the g-ir-* python files >> were specifying python38. I tried building gobject-introspection with 39, but >> fails. I don’t know whether I can classify this as a bug and make a report. >> In >> any case,

Re: Forcing python39 on M1

2021-03-12 Thread Peter West
Attached please find the end of the log. — p...@ehealth.id.au “But if it is by the finger of God that I cast out demons, then the kingdom of God has come upon you.” > On 12 Mar 2021, at 7:36 pm, Peter West wrote: > > Having heard that python39 is the only one (so far) to compile natively on >

Forcing python39 on M1

2021-03-12 Thread Peter West
Having heard that python39 is the only one (so far) to compile natively on M1, I’m trying to force the python ports I use to python39, by creating a local repo and modifying the Portfiles. I ran intoa brick wall with gexiv2, which was because the g-ir-* python files were specifying python38. I