Re: [portgroups] Python
Mojca Miklavec wrote: > Removing any traces of 3.x up to 3.6 should be straightforward, but > requiring quite a bit of (tedious) work. > > Mojca > > PS: just removing the numbers from portgroup is not sufficient. All > ports that don't specify the default version need to be revbumped and > checked that they are compatible with python 3.7 at least, or at least > those should specify the default python version. I've taken the 1st steps : https://trac.macports.org/ticket/59029 https://trac.macports.org/ticket/59030 -- Bjarne D Mathiesen Korsør ; Danmark ; Europa -- denne besked er skrevet i et (næsten) M$-frit miljø MacOS X 10.13.6 High Sierra : 17" 2011 MacBook Pro ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 2012 Mac Pro ; 2 x 3.46GHz 6-Core Xeon ; 48GB MacOS X 10.6.8 Snow Leopard : Mac Mini ; 2GHz Core 2 Duo (64 bit) ; 4GB (3GB actual) 667MHz Mac Mini ; 1.83GHz Core Duo (32 bit) ; 2GB 667Mhz
Re: [portgroups] Python
Bjarne D Mathiesen wrote: > Richard L. Hamilton wrote: >> Depending on the results, with some effort, it might be possible to drop >> some of the intermediate versions. But only if a later suitable (for >> everything dependent on it) version is possible on every supported OS. And >> it would mean bumping portfiles, and rebuilding everything depending on >> dropped versions. It probably wouldn't be worth the bother, and given all >> the constraints, might only get rid of a few versions. >> > > so we've got 2 issues here : > - which pythonXY the pyXY-{name} support > and whether theese can be brought up to python37 > - whether any Portfile that demands a pythonXY that isn't python37 > can be updated to depend on python37 instead > > We'll need some statistict / overview on this matter. > I'll look into this. This ;-) nasty ;-) piece of bash scripting will give an oversigt of all the pyXY-{name} ports and which versions of python they claim to support I'll post a file on my website, when it has finished running :-) Finished : https://macports.mathiesen.info/portfiles/python/pyPorts.txt Optimised/revised script ; runs 9 times faster than the original --- begin bash script --- #!/macports/bin/bash declare -a pyVersions=( 26 27 32 33 34 35 36 37 ) declare -a pyPorts=( $( port -q search --name py- \ | sed -E -e '/^py-/!d' ) ) maxLetters=$( \ for (( i=0 ; i<${#pyPorts[@]} ; i++ )) do echo ${#pyPorts[${i}]} done | sort -u -n | tail -1 ) (( maxLetters+=5 )) for pyPort in ${pyPorts[@]} do printf "%-${maxLetters}s" ${pyPort} subPorts=$( port info --subports --maintainer ${pyPort} ) for V in ${pyVersions[@]} do subCount=$( echo "${subPorts}" | fgrep -c "${V}" ) if [[ "${subCount}" -eq 0 ]] then echo -n " " else echo -n "${V} " fi done echo $( echo ${subPorts} \ | sed -E -e 's/^.*://' -e 's/.* ([^ ]*\@[^ ,]*).*$/\1/' ) done --- end bash script --- -- Bjarne D Mathiesen Korsør ; Danmark ; Europa -- denne besked er skrevet i et (næsten) M$-frit miljø MacOS X 10.13.6 High Sierra : 17" 2011 MacBook Pro ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 2012 Mac Pro ; 2 x 3.46GHz 6-Core Xeon ; 48GB MacOS X 10.6.8 Snow Leopard : Mac Mini ; 2GHz Core 2 Duo (64 bit) ; 4GB (3GB actual) 667MHz Mac Mini ; 1.83GHz Core Duo (32 bit) ; 2GB 667Mhz
Re: [portgroups] Python
* raf: > i hope python27 wont't go away. Would you mind stepping a bit further away? Thanks. :-) -Ralph
Re: [portgroups] Python
Mojca Miklavec wrote: > On Fri, 13 Sep 2019 at 03:51, Bjarne D Mathiesen wrote: >> >> Richard L. Hamilton wrote: >>> Depending on the results, with some effort, it might be possible to drop >>> some of the intermediate versions. But only if a later suitable (for >>> everything dependent on it) version is possible on every supported OS. And >>> it would mean bumping portfiles, and rebuilding everything depending on >>> dropped versions. It probably wouldn't be worth the bother, and given all >>> the constraints, might only get rid of a few versions. >>> >> >> so we've got 2 issues here : >> - which pythonXY the pyXY-{name} support >> and whether theese can be brought up to python37 >> - whether any Portfile that demands a pythonXY that isn't python37 >> can be updated to depend on python37 instead >> >> We'll need some statistict / overview on this matter. >> I'll look into this. >> >> It's also a question about keeping the macports infrastructure up-to-date. >> >> I've eg somehow gotten libsvm installed, and it has : >> Variants: [+]java, [+]python27, python34, [+]tools, universal >> as well as being seriously out-of-date: >> libsvm @3.20_2 -> Version 3.24, September 2019 > > This looks like an obvious example of a port that simply no-one > touched for years and should probably be easy to update, replace > python34 with python37 (as well as make that one default if it works > as expected). I could realitively easily do the upgrade - I've already taken a look at it. Problem is, it's not something I think I've ever used (it was something I installed because of a College Course but they told us to use Anaconda instead) so I'll have no way of testing it in production. $=> port dependents libsvm py37-pymvpa depends on libsvm $=> port info py-pymvpa py-pymvpa @2.6.5_1 (python, science, math) Sub-ports: py27-pymvpa, py34-pymvpa, py35-pymvpa, py36-pymvpa, py37-pymvpa maintainers {stromnov @stromnov} openmaintainer So, I'ld say, it's the responsibility of the maintainer of py-pymvpa to also maintain libsvm. > > In general updating from 2.7 to 3.7 is not always possible, in > particular we still don't have the port for wxWidgets (Phoenix), and > software needs to be rewritten to use that one as well. I know that. It's eg a major problem if you want/need to use utf-8. > > I would say that we'll need to keep 2.7 around, but of course switch > to 3.7 as much as possible. !!! EVERYBODY !!! is in process of switching over to 3.7 : https://python3statement.org/ and ending support for their 2.7 versions on 2020-01-01 > > Personally I don't mind if we remove all traces of Python 2.4-2.6 > which should be very easy. Almost nothing depends on that, it's just > there if someone would want to some extent still run the older python. I've taken the 1st step in that process : https://github.com/macports/macports-ports/pull/5265 > > Removing any traces of 3.x up to 3.6 should be straightforward, but > requiring quite a bit of (tedious) work. I'm willing to undertake that piece of clean-up ;-) Are you of the opinion, that removing 3.5 too will be a good idea ?!? > > Mojca > > PS: just removing the numbers from portgroup is not sufficient. All > ports that don't specify the default version need to be revbumped and > checked that they are compatible with python 3.7 at least, or at least > those should specify the default python version. > n As I've stated in a previous post, the 1st order of the day is to get some stats on the size of the problem. There'll also be the problem of transitioning to 3.8.0 that according to the schedule should have 3.8.0 final: Monday, 2019-10-21 , so IMHO it would be a good idea to plan for that already now. -- Bjarne D Mathiesen Korsør ; Danmark ; Europa -- denne besked er skrevet i et (næsten) M$-frit miljø MacOS X 10.13.6 High Sierra : 17" 2011 MacBook Pro ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 2012 Mac Pro ; 2 x 3.46GHz 6-Core Xeon ; 48GB MacOS X 10.6.8 Snow Leopard : Mac Mini ; 2GHz Core 2 Duo (64 bit) ; 4GB (3GB actual) 667MHz Mac Mini ; 1.83GHz Core Duo (32 bit) ; 2GB 667Mhz
Re: [portgroups] Python
python26 @2.6.9_7 (lang) EOL python27 @2.7.16_2 (lang) EOL 2020-01-01 https://www.python.org/dev/peps/pep-0373/ python32 @3.2.6_8 (lang) EOL python33 @3.3.7_3 (lang) EOL 2017-09-19 python34 @3.4.10_2 (lang) EOL 2019-03-18 https://www.python.org/dev/peps/pep-0429/ python35 @3.5.7_1 (lang) CURRENT https://www.python.org/dev/peps/pep-0478/ python36 @3.6.9_1 (lang) CURRENT https://www.python.org/dev/peps/pep-0494/ python37 @3.7.4_1 (lang) CURRENT https://www.python.org/dev/peps/pep-0537/ python38 @3.8.0b4 (lang) FUTURE https://www.python.org/dev/peps/pep-0569/ -- Bjarne D Mathiesen Korsør ; Danmark ; Europa -- denne besked er skrevet i et (næsten) M$-frit miljø MacOS X 10.13.6 High Sierra : 17" 2011 MacBook Pro ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 2012 Mac Pro ; 2 x 3.46GHz 6-Core Xeon ; 48GB MacOS X 10.6.8 Snow Leopard : Mac Mini ; 2GHz Core 2 Duo (64 bit) ; 4GB (3GB actual) 667MHz Mac Mini ; 1.83GHz Core Duo (32 bit) ; 2GB 667Mhz
Re: [portgroups] Python
On Fri, 13 Sep 2019 at 03:51, Bjarne D Mathiesen wrote: > > Richard L. Hamilton wrote: > > Depending on the results, with some effort, it might be possible to drop > > some of the intermediate versions. But only if a later suitable (for > > everything dependent on it) version is possible on every supported OS. And > > it would mean bumping portfiles, and rebuilding everything depending on > > dropped versions. It probably wouldn't be worth the bother, and given all > > the constraints, might only get rid of a few versions. > > > > so we've got 2 issues here : > - which pythonXY the pyXY-{name} support > and whether theese can be brought up to python37 > - whether any Portfile that demands a pythonXY that isn't python37 > can be updated to depend on python37 instead > > We'll need some statistict / overview on this matter. > I'll look into this. > > It's also a question about keeping the macports infrastructure up-to-date. > > I've eg somehow gotten libsvm installed, and it has : > Variants: [+]java, [+]python27, python34, [+]tools, universal > as well as being seriously out-of-date: > libsvm @3.20_2 -> Version 3.24, September 2019 This looks like an obvious example of a port that simply no-one touched for years and should probably be easy to update, replace python34 with python37 (as well as make that one default if it works as expected). In general updating from 2.7 to 3.7 is not always possible, in particular we still don't have the port for wxWidgets (Phoenix), and software needs to be rewritten to use that one as well. I would say that we'll need to keep 2.7 around, but of course switch to 3.7 as much as possible. Personally I don't mind if we remove all traces of Python 2.4-2.6 which should be very easy. Almost nothing depends on that, it's just there if someone would want to some extent still run the older python. Removing any traces of 3.x up to 3.6 should be straightforward, but requiring quite a bit of (tedious) work. Mojca PS: just removing the numbers from portgroup is not sufficient. All ports that don't specify the default version need to be revbumped and checked that they are compatible with python 3.7 at least, or at least those should specify the default python version.
Re: [portgroups] Python
raf wrote: > > i hope python27 wont't go away. > > cheers, > raf https://pythonclock.org/ -- Bjarne D Mathiesen Korsør ; Danmark ; Europa -- denne besked er skrevet i et (næsten) M$-frit miljø MacOS X 10.13.6 High Sierra : 17" 2011 MacBook Pro ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 2012 Mac Pro ; 2 x 3.46GHz 6-Core Xeon ; 48GB MacOS X 10.6.8 Snow Leopard : Mac Mini ; 2GHz Core 2 Duo (64 bit) ; 4GB (3GB actual) 667MHz Mac Mini ; 1.83GHz Core Duo (32 bit) ; 2GB 667Mhz
Re: [portgroups] Python
Bjarne D Mathiesen wrote: > Richard L. Hamilton wrote: >> Depending on the results, with some effort, it might be possible to drop >> some of the intermediate versions. But only if a later suitable (for >> everything dependent on it) version is possible on every supported OS. And >> it would mean bumping portfiles, and rebuilding everything depending on >> dropped versions. It probably wouldn't be worth the bother, and given all >> the constraints, might only get rid of a few versions. >> > > so we've got 2 issues here : > - which pythonXY the pyXY-{name} support > and whether theese can be brought up to python37 > - whether any Portfile that demands a pythonXY that isn't python37 > can be updated to depend on python37 instead > > We'll need some statistict / overview on this matter. > I'll look into this. This ;-) nasty ;-) piece of bash scripting will give an oversigt of all the pyXY-{name} ports and which versions of python they claim to support I'll post a file on my website, when it has finished running :-) --- begin bash script --- declare -a pyVersions=( 26 27 32 33 34 35 36 37 ) pyPorts=( $( \ ( for V in ${pyVersions[@]} do port -q search --name py${V} | sed -E -e "s/${V}//" done ) | sort -u ) ) maxLetters=$( \ for (( i=0 ; i<${#pyPorts[@]} ; i++ )) do echo ${#pyPorts[${i}]} done | sort -u -n | tail -1 ) (( maxLetters+=5 )) for pyPort in ${pyPorts[@]} do printf "%-${maxLetters}s" ${pyPort} for V in ${pyVersions[@]} do isPort=$( port -q search ${pyPort/-/${V}-} ) if [[ -z "${isPort}" ]] then echo -n " " else echo -n "${V} " fi done echo done --- end bash script --- -- Bjarne D Mathiesen Korsør ; Danmark ; Europa -- denne besked er skrevet i et (næsten) M$-frit miljø MacOS X 10.13.6 High Sierra : 17" 2011 MacBook Pro ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 2012 Mac Pro ; 2 x 3.46GHz 6-Core Xeon ; 48GB MacOS X 10.6.8 Snow Leopard : Mac Mini ; 2GHz Core 2 Duo (64 bit) ; 4GB (3GB actual) 667MHz Mac Mini ; 1.83GHz Core Duo (32 bit) ; 2GB 667Mhz
Re: [portgroups] Python
Bjarne D Mathiesen wrote: > Richard L. Hamilton wrote: > > Depending on the results, with some effort, it might be possible to > > drop some of the intermediate versions. But only if a later suitable > > (for everything dependent on it) version is possible on every > > supported OS. And it would mean bumping portfiles, and rebuilding > > everything depending on dropped versions. It probably wouldn't be > > worth the bother, and given all the constraints, might only get rid > > of a few versions. > > > > so we've got 2 issues here : > - which pythonXY the pyXY-{name} support > and whether theese can be brought up to python37 > - whether any Portfile that demands a pythonXY that isn't python37 > can be updated to depend on python37 instead > > We'll need some statistict / overview on this matter. > I'll look into this. > > It's also a question about keeping the macports infrastructure up-to-date. > > I've eg somehow gotten libsvm installed, and it has : > Variants: [+]java, [+]python27, python34, [+]tools, universal > as well as being seriously out-of-date: > libsvm @3.20_2 -> Version 3.24, September 2019 > > -- > Bjarne D Mathiesen > Korsør ; Danmark ; Europa i hope python27 wont't go away. cheers, raf
Re: [portgroups] Python
Richard L. Hamilton wrote: > Depending on the results, with some effort, it might be possible to drop some > of the intermediate versions. But only if a later suitable (for everything > dependent on it) version is possible on every supported OS. And it would mean > bumping portfiles, and rebuilding everything depending on dropped versions. > It probably wouldn't be worth the bother, and given all the constraints, > might only get rid of a few versions. > so we've got 2 issues here : - which pythonXY the pyXY-{name} support and whether theese can be brought up to python37 - whether any Portfile that demands a pythonXY that isn't python37 can be updated to depend on python37 instead We'll need some statistict / overview on this matter. I'll look into this. It's also a question about keeping the macports infrastructure up-to-date. I've eg somehow gotten libsvm installed, and it has : Variants: [+]java, [+]python27, python34, [+]tools, universal as well as being seriously out-of-date: libsvm @3.20_2 -> Version 3.24, September 2019 -- Bjarne D Mathiesen Korsør ; Danmark ; Europa -- denne besked er skrevet i et (næsten) M$-frit miljø MacOS X 10.13.6 High Sierra : 17" 2011 MacBook Pro ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 2012 Mac Pro ; 2 x 3.46GHz 6-Core Xeon ; 48GB MacOS X 10.6.8 Snow Leopard : Mac Mini ; 2GHz Core 2 Duo (64 bit) ; 4GB (3GB actual) 667MHz Mac Mini ; 1.83GHz Core Duo (32 bit) ; 2GB 667Mhz
Re: [portgroups] Python
Richard L. Hamilton wrote: > One might wonder at the number of python version ports. I suspect a couple > of things that I don't know without a lot of digging would provide some > perspective: > * the OS version of python on the earliest OS MacPorts supports, and on each > subsequent OS version I've got both py27 & py37 running on 10.6.8 {i386,x86_64} so the OS is not a problem > * the python versions specifically required by various other ports (not just > x.y or later, and esp. not just 2.y or 3.y) > and maybe > * the degree of change policy for python minor versions (impacting not only > the previous point, but and non-MacPorts software that might be dependent on > a particular version)> (as the recent openssl switchover showed, some > software has backwards compatibility issues with what are supposedly minor version changes) In my experience with python3 then if it works in python3x then it also works in python3x++ The big transitions were python25 -> python26 python31 -> python32 and python27 is fundamentally incompatible with python37; eg the support for utf-8 -- Bjarne D Mathiesen Korsør ; Danmark ; Europa -- denne besked er skrevet i et (næsten) M$-frit miljø MacOS X 10.13.6 High Sierra : 17" 2011 MacBook Pro ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 2012 Mac Pro ; 2 x 3.46GHz 6-Core Xeon ; 48GB MacOS X 10.6.8 Snow Leopard : Mac Mini ; 2GHz Core 2 Duo (64 bit) ; 4GB (3GB actual) 667MHz Mac Mini ; 1.83GHz Core Duo (32 bit) ; 2GB 667Mhz
Re: [portgroups] Python
One might wonder at the number of python version ports. I suspect a couple of things that I don't know without a lot of digging would provide some perspective: * the OS version of python on the earliest OS MacPorts supports, and on each subsequent OS version * the python versions specifically required by various other ports (not just x.y or later, and esp. not just 2.y or 3.y) and maybe * the degree of change policy for python minor versions (impacting not only the previous point, but and non-MacPorts software that might be dependent on a particular version) (as the recent openssl switchover showed, some software has backwards compatibility issues with what are supposedly minor version changes) Depending on the results, with some effort, it might be possible to drop some of the intermediate versions. But only if a later suitable (for everything dependent on it) version is possible on every supported OS. And it would mean bumping portfiles, and rebuilding everything depending on dropped versions. It probably wouldn't be worth the bother, and given all the constraints, might only get rid of a few versions. Compared to some of the even larger ports, or certain ports that do exhaustive optimization, python versions aren't _that_ slow to build, so the only major gain would be space. > On Sep 12, 2019, at 17:32, Bjarne D Mathiesen > wrote: > > > > Christopher Jones wrote: >> >> Depends what you are thinking of by ‘officially support’. >> >> We have ports for >> >> python26 @2.6.9_7 (lang) >> python27 @2.7.16_2 (lang) >> >> python32 @3.2.6_8 (lang) >> python33 @3.3.7_3 (lang) >> python34 @3.4.10_2 (lang) >> python35 @3.5.7_1 (lang) >> python36 @3.6.9_1 (lang) >> python37 @3.7.4_1 (lang) >> >> However, that does not mean each of the various ‘py’ ports support all of >> the above.. > > I know that. > I'm limiting myself to only bothering with python27 & python37 > > I could possibly without any problems just plug the rest in with a good > chance of success; but one of the python program I've made as Portfile > for says : 3.3 and above > >>> On 12 Sep 2019, at 9:09 pm, Bjarne D Mathiesen >>> wrote: >>> >>> Which versions of Python do macports still officially support ?!? >>> > > I've had a bit of discussion about supporting python27 in >https://github.com/macports/macports-ports/pull/5256 > and took at look at the python-1.0.tcl file > > Now, python-1.0.tcl >- sets python27 as the default > with IMHO is a bad idea as it's been on the death-bed for several > years now; and is being EOLed in 2020 >- there's still a lot of py24 & py25 cruft in there > so I was thinking about >1 setting python37 as the default >2 removing all the py24 & py25 stuff > > Possibly, also EOL / obsolete python3[2-5] & python26 > > -- > Bjarne D Mathiesen > Korsør ; Danmark ; Europa > -- > denne besked er skrevet i et (næsten) M$-frit miljø > MacOS X 10.13.6 High Sierra : > 17" 2011 MacBook Pro ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 > 2012 Mac Pro ; 2 x 3.46GHz 6-Core Xeon ; 48GB > MacOS X 10.6.8 Snow Leopard : > Mac Mini ; 2GHz Core 2 Duo (64 bit) ; 4GB (3GB actual) 667MHz > Mac Mini ; 1.83GHz Core Duo (32 bit) ; 2GB 667Mhz >
Re: [portgroups] Python
Christopher Jones wrote: > > Depends what you are thinking of by ‘officially support’. > > We have ports for > > python26 @2.6.9_7 (lang) > python27 @2.7.16_2 (lang) > > python32 @3.2.6_8 (lang) > python33 @3.3.7_3 (lang) > python34 @3.4.10_2 (lang) > python35 @3.5.7_1 (lang) > python36 @3.6.9_1 (lang) > python37 @3.7.4_1 (lang) > > However, that does not mean each of the various ‘py’ ports support all of the > above.. I know that. I'm limiting myself to only bothering with python27 & python37 I could possibly without any problems just plug the rest in with a good chance of success; but one of the python program I've made as Portfile for says : 3.3 and above >> On 12 Sep 2019, at 9:09 pm, Bjarne D Mathiesen >> wrote: >> >> Which versions of Python do macports still officially support ?!? >> I've had a bit of discussion about supporting python27 in https://github.com/macports/macports-ports/pull/5256 and took at look at the python-1.0.tcl file Now, python-1.0.tcl - sets python27 as the default with IMHO is a bad idea as it's been on the death-bed for several years now; and is being EOLed in 2020 - there's still a lot of py24 & py25 cruft in there so I was thinking about 1 setting python37 as the default 2 removing all the py24 & py25 stuff Possibly, also EOL / obsolete python3[2-5] & python26 -- Bjarne D Mathiesen Korsør ; Danmark ; Europa -- denne besked er skrevet i et (næsten) M$-frit miljø MacOS X 10.13.6 High Sierra : 17" 2011 MacBook Pro ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 2012 Mac Pro ; 2 x 3.46GHz 6-Core Xeon ; 48GB MacOS X 10.6.8 Snow Leopard : Mac Mini ; 2GHz Core 2 Duo (64 bit) ; 4GB (3GB actual) 667MHz Mac Mini ; 1.83GHz Core Duo (32 bit) ; 2GB 667Mhz
Re: [portgroups] Python
Depends what you are thinking of by ‘officially support’. We have ports for python26 @2.6.9_7 (lang) An interpreted, object-oriented programming language python27 @2.7.16_2 (lang) An interpreted, object-oriented programming language python27-bootstrap @2.7.16_2 (lang) An interpreted, object-oriented programming language python32 @3.2.6_8 (lang) An interpreted, object-oriented programming language python33 @3.3.7_3 (lang) An interpreted, object-oriented programming language python34 @3.4.10_2 (lang) An interpreted, object-oriented programming language python35 @3.5.7_1 (lang) An interpreted, object-oriented programming language python36 @3.6.9_1 (lang) An interpreted, object-oriented programming language python37 @3.7.4_1 (lang) An interpreted, object-oriented programming language However, that does not mean each of the various ‘py’ ports support all of the above.. Chris > On 12 Sep 2019, at 9:09 pm, Bjarne D Mathiesen > wrote: > > Which versions of Python do macports still officially support ?!? > > -- > Bjarne D Mathiesen > Korsør ; Danmark ; Europa > -- > denne besked er skrevet i et (næsten) M$-frit miljø > MacOS X 10.13.6 High Sierra : > 17" 2011 MacBook Pro ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 > 2012 Mac Pro ; 2 x 3.46GHz 6-Core Xeon ; 48GB > MacOS X 10.6.8 Snow Leopard : > Mac Mini ; 2GHz Core 2 Duo (64 bit) ; 4GB (3GB actual) 667MHz > Mac Mini ; 1.83GHz Core Duo (32 bit) ; 2GB 667Mhz smime.p7s Description: S/MIME cryptographic signature
[portgroups] Python
Which versions of Python do macports still officially support ?!? -- Bjarne D Mathiesen Korsør ; Danmark ; Europa -- denne besked er skrevet i et (næsten) M$-frit miljø MacOS X 10.13.6 High Sierra : 17" 2011 MacBook Pro ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 2012 Mac Pro ; 2 x 3.46GHz 6-Core Xeon ; 48GB MacOS X 10.6.8 Snow Leopard : Mac Mini ; 2GHz Core 2 Duo (64 bit) ; 4GB (3GB actual) 667MHz Mac Mini ; 1.83GHz Core Duo (32 bit) ; 2GB 667Mhz