Hi,
Bill Cole wrote:
But this was easy to find:https://docs.python.org/3.11/library/imp.html and it
seems to indicate that you should backrev your Python to 3.11 at most.
seamonkey dev guys told me indeed 3.12 is not compatible, I selected
python 3.11 and compilation begins... fails now in
Python's imp module was deprecated in Python 3.4 in favor of ‘importlib’, and
removed in Python 3.12.
This is confirmed by the deprecation warning printed by Python 3.11, which does
still have the imp module:
❯ /opt/local/bin/python3.11
Python 3.11.10 (main, Sep 7 2024, 05:47:53) [
On 2024-09-10 at 16:02:06 UTC-0400 (Tue, 10 Sep 2024 22:02:06 +0200)
Riccardo Mottola via macports-users
is rumored to have said:
> I understand it is not finding module “imp”. I wonder if my python 3.12
> misses some module to isntall? any python expert here?
I am NOT a python exp
requires python3 and also
somehow wants an internal python?
$ MACH_USE_SYSTEM_PYTHON=1 ./mach build
should convince it to use system python, which should be python3, so almost
easier as the legacy python2.7 for ArcticFox and similar.
I did use python select and so now I have:
$ python3 --version
On Mon, Aug 26, 2024 at 01:19:32PM +0200, "René J.V. Bertin"
wrote:
> Hi,
>
> This is one of those periods where I notice that "damn, I should
> update my Perl5 and/or Python interpreters, but then I'll also have to
> reinstall a whole bunch of modules for t
Hi,
This is one of those periods where I notice that "damn, I should update my
Perl5 and/or Python interpreters, but then I'll also have to reinstall a whole
bunch of modules for them and figure out which old ones I can throw out". MAYBE
that would be easier if I kept my enti
On Wed, May 1, 2024, at 5:04 PM, Rainer Müller wrote:
> On 01/05/2024 23.17, ideal.cat9...@fastmail.com wrote:
>> I’m relatively new to MacPorts, and I notice that the pythonX packages
>> create a python but not python3 link. Is there a reason for that? Both
>> the system pyt
On 01/05/2024 23.17, ideal.cat9...@fastmail.com wrote:
> I’m relatively new to MacPorts, and I notice that the pythonX packages
> create a python but not python3 link. Is there a reason for that? Both
> the system python and other package managers use python3, and that’s a
> hard hab
I’m relatively new to MacPorts, and I notice that the pythonX packages create a
python but not python3 link. Is there a reason for that? Both the system python
and other package managers use python3, and that’s a hard habit to switch after
so many years, and I don’t want to accidentally use the
Whoever fixed borgbackup, I appreciate it. It is a great relief to
have backups working again.
Thanks,
Ken Wolcott
On Sun, Mar 3, 2024 at 5:58 PM Kenneth Wolcott wrote:
>
> It loos like this problem has re-appeared :-(
>
> You do not have a supported version of the msgpack py
It loos like this problem has re-appeared :-(
You do not have a supported version of the msgpack python package
installed. Terminating.
This should never happen as specific, supported versions are required
by our setup.py.
Do not contact borgbackup support about this.
terminating with error
On 6/1/2024 00:07, Clemens Lang wrote:
Actually, the relevant commit is
https://github.com/borgbackup/borg/commit/39761ebadc9325a7cc7e931144e2709effe8f0f0,
and that has been backported to the 1.2 branch of borgbackup and is in
1.2.7, so just make sure you have the latest borgbackup installed and
On 5/1/2024 23:45, Clemens Lang wrote:
For reasons I don't understand, borgbackup wants to allow-list every new
version of the msgpack library manually, so every update of the msgpack
library breaks borgbackup.
It's likely because many python module projects have a culture of
Hi again,
On Fri, Jan 05, 2024 at 01:45:46PM +0100, Clemens Lang wrote:
> On Thu, Dec 28, 2023 at 10:42:25PM -0800, Kenneth Wolcott wrote:
> > You do not have a supported version of the msgpack python package
> > installed. Terminating.
> > This should never happen as specifi
Hi,
On Thu, Dec 28, 2023 at 10:42:25PM -0800, Kenneth Wolcott wrote:
> You do not have a supported version of the msgpack python package
> installed. Terminating.
> This should never happen as specific, supported versions are required
> by our setup.py.
> Do not contact borgbacku
On Sat, Dec 30, 2023 at 06:38:15PM -0800, Kenneth Wolcott
wrote:
> Hi;
>
> How to wean myself away from Python 3.9? and then Python3.10?
>
> There's so much that I don't understand about MacPorts.
>
> Should I uninstall everything that depends on Python 3.9 an
I do something like this:
export OLDV=39 NEWV=310
sudo -E port -pNc install "python${NEWV}" $(port installed "py${OLDV}-*" | sed
-E -e "s/[[:space:]]+py${OLDV}/py${NEWV}/" | cut -d " " -f1 | tr '\n' ' ')
sudo port uninstall "
Hi;
How to wean myself away from Python 3.9? and then Python3.10?
There's so much that I don't understand about MacPorts.
Should I uninstall everything that depends on Python 3.9 and then
Python 3.9 and then re-install those apps that I uninstalled from the
first sequence? How wil
borgbackup
borgbackup @1.2.3_0
borgbackup @1.2.3_1
borgbackup @1.2.4_0
borgbackup @1.2.6_0 (active)
On Thu, Dec 28, 2023 at 10:42 PM Kenneth Wolcott
wrote:
>
> You do not have a supported version of the msgpack python package
> installed. Terminating.
> This should never happen
You do not have a supported version of the msgpack python package
installed. Terminating.
This should never happen as specific, supported versions are required
by our setup.py.
Do not contact borgbackup support about this.
terminating with error status, rc 2
Thanks,
Ken Wolcott
cshrc, .bashrc, or whatever environment
you're running.
Exit the terminal / start a new terminal
This terminal should not have loaded any anaconda environments and
whatever python version you had installed should be working as
before. Where does /opt/local/bin/python3 point?
Dr Bal
Hi all,
If I want to completely remove installed anaconda python and
associated package,
Should I use the following command?
"conda remove --all"
Thanks
Tao
On 4/29/23 10:46 AM, Tao Zhang wrote:
My .cshrc file is not changed. The only changed file is .bash_profile
(see
lize and <<<< conda
initialize in the .cshrc, .bashrc, or whatever environment you're running.
Exit the terminal / start a new terminal
This terminal should not have loaded any anaconda environments and
whatever python version you had installed should be working as befo
Hi Balthasar & all,
After I installed Anaconda python, previous command "python3" and
abbreviation does not work anymore (see 1)
I use .cshrc (see 2) file. I find that .bash_profile is changed (see 3).
I use "conda deactivate" to exit the Anaconda python, it does
Hi Marius,
How to check what python ports (package) I have already installed
through Macport?
How to install the following additional package through Macport?
Thanks
Tao
conda install -c conda-forge cartopy
conda install -c conda-forge h5netcdf
conda install -c conda-forge xarray
conda
workshop, add it back to
the beginning of the `PATH` and install the packages. Make sure that
it’s getting installed somewhere on its own (especially not to
`/opt/local`).
hope that helps!
ak
On 2023-04-28 (KW 17) at 19:13:51 (-0500) Tao Zhang wrote:
Hi, all
I want to attend a python
Hi, all
I want to attend a python workshop which requires the installation of
Anaconda Python, see the info. below.
Since I have already installed python in my Macbook pro through
Macport (see info. below),
I am asking if I still need to install Anaconda Python?
Does this Anaconda
I'm on MacOSX 10.5 Tiger, PPC architecture.
Ipython (3.11.2 currently but already had the same with earlier
verions of atleast 3.10 and 3.11) installs fine. But trying to use it
(without any further args, just as command shell) bombs (see below).
Piping into or redirecting input works fine.
Putt
Hi!
I was using happily meld on High Sierra, it is a quite powerful
recursive diff tool I use - unfortunately written in python.
It used to work fine on MacOS 10.13
In one of the relatively recent updates (about a week) it developed
glitches in the tree view display of all files, where files
)trac.macports.orghth--ferdyOn 19 Feb 2023, at 16:34, Artemio González López via macports-users wrote:Since last week or so, I haven’t been able to update my python 3.10. I believe the relevant error is the following:make[1]: Entering directory `/opt/local/var/macports/build
Since last week or so, I haven’t been able to update my python 3.10. I believe
the relevant error is the following:
make[1]: Entering directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/Python
Hi all.
I don't remember where, but I know I configure this machine to ignore
precompiled and do compile all on local machine... this as precondition. 😇
After "selfupdate" I install first and only "wget"... which include a python
version (Python 3.10.8). It needs a lo
Tom Gederberg wrote:
It appears that you can either install Python modules (py310-matplotlib,
py310-numpy, etc) either directly from MacPorts or you can install pip (for
example py30-pip) with MacPorts and then use pip to install the modules.
Is there a recommendation on which way to go
* Thomas Gederberg:
> It appears that you can either install Python modules
> (py310-matplotlib, py310-numpy, etc) either directly from MacPorts or
> you can install pip (for example py30-pip) with MacPorts and then use
> pip to install the modules.
The issue with installing Python m
docker's a heavyweight solution.
Use Python's virtualenv.
Then you can pip install whatever and not corrupt your macports install.
On Tue, Dec 6, 2022 at 7:27 AM David Herron wrote:
> Let me recommend Docker. You can use the Python base image, to select
> your preferred Pyt
Let me recommend Docker. You can use the Python base image, to select your
preferred Python version, and then run pip or pip3 (as appropriate) in the
Dockerfile. This way installed dependencies are neatly encapsulated, they
do not pollute your host environment, and you have documentation of how
Generally, use MacPorts for a newer python/pip and use that pip to
install subsequent modules.
There are a few cases where you may benefit from MacPorts' pre-compiled
c modules, however you won't be able to version-pin dependencies
(MacPorts doesn't appear to have this concep
Not a heavy user of python, but a "quick and dirty" answer would be: installing
and updating via pip might give you the latest version faster, but you need to
remember to check for updates via pip. Installing via MacPorts would allow you
to update python packages together with every
It appears that you can either install Python modules (py310-matplotlib,
py310-numpy, etc) either directly from MacPorts or you can install pip (for
example py30-pip) with MacPorts and then use pip to install the modules.
Is there a recommendation on which way to go?
Tom Gederberg
On Nov 9, 2022, at 17:57, supervisitor wrote:
> ... ups, this I have probably overlooked. (have made the installation from
> source).
>
> But before I now uninstall everything to perform a reinstall, some further
> questions:
>
> Can I do an installation with parameter "--with-applications-dir
on this?
>> Thanks and cheers!
>>>> On 9 Nov 2022, at 16:54, Langer, Stephen A. (Fed)
>>>> wrote:
>>>
>>> Build MacPorts from source and use the --with-applications-dir option when
>>> configuring it.
>>>
>>> -- Steve
>
ild MacPorts from source and use the --with-applications-dir option when
configuring it.
-- Steve
-Original Message-
From: macports-users on behalf of
supervisitor via macports-users
Reply-To: supervisitor
Date: Wednesday, November 9, 2022 at 10:38 AM
To: "macports-users@list
t; Reply-To: supervisitor
> Date: Wednesday, November 9, 2022 at 10:38 AM
> To: "macports-users@lists.macports.org"
> Subject: how to move "Python Launcher" away from /Application folder?
>
>Hi.
>
>This "MacPorts" folder inside Applications, wh
users@lists.macports.org"
Subject: how to move "Python Launcher" away from /Application folder?
Hi.
This "MacPorts" folder inside Applications, where the Python Launcher is
inside, looks useless for me... but is needed when I launch "port -v upgrade
outdated"
Hi.
This "MacPorts" folder inside Applications, where the Python Launcher is
inside, looks useless for me... but is needed when I launch "port -v upgrade
outdated" from terminal.
=> does someone know a solution to move this folder and files inside away from
there, be
.nl/the-book/>
Book: Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>
> On 1 May 2022, at 07:03, Mike Alexander wrote:
>
> On 30 Apr 2022, at 6:26, Al Varnell wrote:
>
>> Or just install python.
>
> It is installed. The problem is that the Combine PDF Pag
On Apr 30, 2022, at 02:08, Mike Alexander wrote:
> However there is at least one thing Apple installed that depends on Python.
> The Automator action "Combine PDF Pages" fails because it tries to use the
> copy of Python that has been removed.
I trust you have reported this problem to Apple.
On 30 Apr 2022, at 6:26, Al Varnell wrote:
> Or just install python.
It is installed. The problem is that the Combine PDF Pages Automator action is
in /system/library and has a hard coded path to /usr/bin/python. That can't be
worked around since nothing in /System can be changed.
> On Apr 30, 2022, at 06:27, Al Varnell via macports-users
> wrote:
>
> On Apr 30, 2022, at 12:08 AM, Mike Alexander wrote:
>>
>>> On 23 Apr 2022, at 8:06, Steven Smith wrote:
>>>
>>> The only issue I’ve seen with the disappearance of macOS
On Apr 30, 2022, at 12:08 AM, Mike Alexander wrote:
>
> On 23 Apr 2022, at 8:06, Steven Smith wrote:
>
>> The only issue I’ve seen with the disappearance of macOS native Python is
>> some minor thing my own preliminary calendar-contacts-server
>> configuration—t
On 23 Apr 2022, at 8:06, Steven Smith wrote:
The only issue I’ve seen with the disappearance of macOS native
Python is some minor thing my own preliminary calendar-contacts-server
configuration—the “fix” in response to the update was just to
install the MacPorts version.
I'm also on 1
I’m on 12.3.1 with all those ports and there’s no issue. I’ve contributed
directly to several of these and have always made sure that everything uses the
MacPorts Python dependencies, both in depends_build and depends_lib/run.
Additionally, to the best of my knowledge, there’s nothing in the
On Sun, Apr 17, 2022 at 09:47:57AM -0500, Ryan Schmidt wrote:
>
>
> On Apr 17, 2022, at 09:45, Christian Calderon wrote:
>
> >> You would not be able to make a symbolic link at /usr/bin/python because
> >> /usr/bin is a protected directory.
> >
> >
> On 17 Apr 2022, at 16:47, Ryan Schmidt wrote:
>
>
>
> On Apr 17, 2022, at 09:45, Christian Calderon wrote:
>
>>> You would not be able to make a symbolic link at /usr/bin/python because
>>> /usr/bin is a protected directory.
>>
>> TIL. Is
susing the migration instructions (an unnecessary ‘migration')
in an attempt to do an as-clean-as-possible build with the largest chance to
run into any hidden dependency on the availability of /usr/bin/python.
Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>)
R&
On Apr 17, 2022, at 09:45, Christian Calderon wrote:
>> You would not be able to make a symbolic link at /usr/bin/python because
>> /usr/bin is a protected directory.
>
> TIL. Is that something I could work around by disabling SIP?
On macOS 10.x, yes. On macOS 11 and later
> You would not be able to make a symbolic link at /usr/bin/python because
> /usr/bin is a protected directory.
TIL. Is that something I could work around by disabling SIP?
And of course I would make a ticket but I’d also try to get stuff working
locally since proper fixes can take time.
On Apr 17, 2022, at 09:13, Christian Calderon wrote:
> I’m on 12.3 on all my macs, and I haven’t noticed anything broken in MacPorts
> because of the removal of python. If I ram into something that needed
> /usr/bin/python I’d just make a symbolic link to MacPorts python 2.
You wou
I’m on 12.3 on all my macs, and I haven’t noticed anything broken in MacPorts
because of the removal of python. If I ram into something that needed
/usr/bin/python I’d just make a symbolic link to MacPorts python 2.
Sent from my iPhone
> On Apr 17, 2022, at 6:50 AM, Gerben Wierda via macpo
On Apr 17, 2022, at 08:49, Gerben Wierda wrote:
> The question I have when moving from 12.2 to 12.3 is: is there a port in my
> set that depends on /usr/bin/python (and should become dependent on a
> MacPorts python instead)?
There are innumerable ways that python might be refere
> On 17 Apr 2022, at 15:22, Ryan Schmidt wrote:
>
>> I’m about to take the plunge and move one of my systems to macOS 12.3 (which
>> removes /usr/bin/python). I am going to consider that a MacPorts major
>> migration (so following the migration instructions).
>
On Apr 16, 2022, at 08:43, Ralph Seichter wrote:
>
> It is also worth mentioning that I use this machine for a lot of Python
> software development. Works just fine.
The python ports and the python module ports are not the ones that are affected
by the problem. The ones affected by th
On Apr 16, 2022, at 08:16, Gerben Wierda wrote:
> I’m about to take the plunge and move one of my systems to macOS 12.3 (which
> removes /usr/bin/python). I am going to consider that a MacPorts major
> migration (so following the migration instructions).
If you are upgrading from macO
+perl5_28 (active)
unbound @1.15.0_0 (active)
wget @1.21.3_0+gnutls (active)
% which python
python not found
% which python3
/usr/bin/python3
Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>)
R&A IT Strategy <https://ea.rna.nl/> (main site)
Book: Chess and the A
Hi,
On Sat, Apr 16, 2022 at 03:16:21PM +0200, Gerben Wierda via macports-users
wrote:
> I’m about to take the plunge and move one of my systems to macOS 12.3
> (which removes /usr/bin/python). I am going to consider that a
> MacPorts major migration (so following the migration ins
* Ralph Seichter via macports-users:
> I'm running a combination of macOS 12.3.1 and MacPorts 2.7.2 on an
> Intel-based MacBook Pro without any problems.
It is also worth mentioning that I use this machine for a lot of Python
software development. Works just fine.
-Ralph
* Gerben Wierda via macports-users:
> I’m about to take the plunge and move one of my systems to macOS 12.3
> (which removes /usr/bin/python). I am going to consider that a
> MacPorts major migration (so following the migration instructions).
I'm running a combination of ma
One of the Mac I manage is on 12.3 (M1 processor). I’ve made a fresh MacPorts
installation, and installed the usual packages needed for our environment. Must
say that we don’t do any Python ourselves there, but several Python packages
are installed as dependencies in the process, and all
I’m about to take the plunge and move one of my systems to macOS 12.3 (which
removes /usr/bin/python). I am going to consider that a MacPorts major
migration (so following the migration instructions).
I haven’t seen any traffic on this issue. Does that mean hardly anyone is on
12.3? Is anyone
On Mar 27, 2022, at 12:48, dan d. wrote:
> Can one delete older python versions then the current python10? Do some
> ports anticipate an older version?
You can uninstall any ports you no longer need or want to have installed. If
any installed ports still declare dependencies on them, Ma
-- ent- XR
Can one delete older python versions then the current python10? Do some ports
anticipate an older version?
Thanks
On Mar 18, 2022, at 03:16, VACCARI FRANCO wrote:
> So, is it considered “safe” in MacPorts’ view to update to MacOS 12.3 and
> Xcode 13.3? I remember a warning on the list about this, due to Python 2.x
> removal from Apple
My recommendations posted last month are unchange
to the now deprecated macOS
Python libraries to MacPorts binaries [search MacPorts Portfiles for plenty of
example uses.]
…
WIN
Or: Try setting `export PYTHON=` in such a way that
the app launch knows about this variable.
> On Mar 18, 2022, at 4:23 PM, Tom wrote:
>
> World of Tank
World of Tanks crashes with this error log. Can there be something done about
it?
> Termination Reason:Namespace DYLD, Code 1 Library missing
> Library not loaded:
> /System/Library/Frameworks/Python.framework/Versions/2.7/Python
> Referenced from: /Volumes/VOLUME/*/Wargam
I just recently upgraded one of my machines to macOS 12.3. It has Python 3.8.9
installed in /usr/bin as python3. Being a backsliding miscreant, I have the
MacPorts Python 2.7 installed as my default (and 3.10 for testing).
Jim
3222 NE 89th St
Seattle, WA 98115
(206) 430-0109
> On Mar
So, is it considered “safe” in MacPorts’ view to update to MacOS 12.3 and Xcode
13.3? I remember a warning on the list about this, due to Python 2.x removal
from Apple
Thanks
Franco
> On 18 Mar 2022, at 05:57, Ryan Schmidt wrote:
>
> On Mar 17, 2022, at 21:37, Bill Cole wrote:
>
On Mar 17, 2022, at 21:37, Bill Cole wrote:
> On 2022-03-17 at 17:22:51 UTC-0400 (Thu, 17 Mar 2022 22:22:51 +0100) Tom is
> rumored to have said:
>
>> Hello people, how do I install a python replacement for macOS 12.3?
>
> port install python310 python_select
python_sele
On 2022-03-17 at 17:22:51 UTC-0400 (Thu, 17 Mar 2022 22:22:51 +0100)
Tom
is rumored to have said:
Hello people, how do I install a python replacement for macOS 12.3?
port install python310 python_select
[come back in 20 minutes]
port select python python310
If you need an older version
On Mar 17, 2022, at 16:22, Tom wrote:
> Hello people, how do I install a python replacement for macOS 12.3?
MacPorts offers many versions of Python. Python 2.7 (/usr/bin/python) was
removed in macOS 12.3. If you want to continue to use Python 2.7, you can
install the python27 port:
sudo p
Hello people, how do I install a python replacement for macOS 12.3?
Thanks for the quick replies. I understand installing these in /opt may
cause problems. Looks like I will need to redo my Macports
installation soon (grin). I could try venv, or perhaps just set a
separate PATH that my third-party stuff gets installed into -- once I
figure out how to set t
I'm not very experienced with Python, yet, but with regard to MacPorts,
I'm trying to understand why when I do a pip3 install, or a direct
install from a project tree ie: "python setup.py install" the tool(s)
end up in this directory instead of /opt/local/bin|sbin etc:
On 2022-01-02 at 16:23:34 UTC-0500 (Sun, 2 Jan 2022 16:23:34 -0500)
Forrest Aldrich
is rumored to have said:
I'm not very experienced with Python, yet, but with regard to
MacPorts, I'm trying to understand why when I do a pip3 install, or a
direct install from a project tree i
I'm not very experienced with Python, yet, but with regard to MacPorts,
I'm trying to understand why when I do a pip3 install, or a direct
install from a project tree ie: "python setup.py install" the tool(s)
end up in this directory instead of /opt/local/bin|sbin etc:
> On 10 Dec 2021, at 8:07 pm, SeaQuench wrote:
>
> Output of selfupdate as requested:
>
> $ sudo port selfupdate
> ---> Updating MacPorts base sources using rsync
> Error: Error synchronizing MacPorts sources: command execution failed
> Please run `port -v selfupdate' for details.
> Error:
Output of selfupdate as requested:
$ sudo port selfupdate
---> Updating MacPorts base sources using rsync
Error: Error synchronizing MacPorts sources: command execution failed
Please run `port -v selfupdate' for details.
Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing
Mac
Hi,
Yes, the error is expected. What i am asking is if you get any indication or
not that there was an issue when you run without the verbose flag. If not, then
i think thats a bug we should address.
Chris
> On 10 Dec 2021, at 7:18 pm, SeaQuench wrote:
>
> I am behind a firewall, so this is
I am behind a firewall, so this is the following is predictable:
$ sudo port -v selfupdate
---> Updating MacPorts base sources using rsync
rsync: failed to connect to rsync.macports.org: Operation timed out (60)
rsync error: error in socket IO (code 10) at
/AppleInternal/BuildRoot/Library/Caches
Just to be clear, are you saying running
> sudo port selfupdate
ran without warnings or error, but did not actually update ? If thats the case
we should file a bug against base as if the rsync fails it should indicate this
to the user ?
cheers Chris
> On 10 Dec 2021, at 3:13 pm, SeaQuench w
Ryan is correct; I had been sync'ing my port index successfully, but MacPorts
itself grew stale due to my being unable to run selfupdate. The MacPorts
Migration Guide suggested a manual update (i.e. reinstall) which I believe got
me going again. Thanks guys! ~SeaQuench
‐‐‐ Original Message
On Dec 10, 2021, at 02:29, Chris Jones wrote:
>
> On 9 Dec 2021, at 10:49 pm, SeaQuench wrote:
>>
>>
>> After downloading and installing the latest MacPorts for Catalina, I
>> followed the instructions to migrate MacPorts:
>> https://trac.macports.org/wiki/Migration
>> Reinstalling the ports
gt;> > sudo port selfupdate
>> > sudo port sync
>> > sudo port upgrade outdated
>>
>> Chris
>>
>>>> On 9 Dec 2021, at 6:53 pm, SeaQuench via macports-users
>>>> wrote:
>>>
>>>
>>>
>>> A
SeaQuench wrote:
After applying an update to MacOS last August, the python ports are reporting a
dependency on either openssl11 or openssl3, neither of which are to be found in
the (local?) index for MacPorts, according to the error I have received, copied
below. While I am prompted to
ort selfupdate
> sudo port sync
> sudo port upgrade outdated
Chris
> On 9 Dec 2021, at 6:53 pm, SeaQuench via macports-users
> wrote:
>
>
> After applying an update to MacOS last August, the python ports are reporting
> a dependency on either openssl11 or openssl3, neither
After applying an update to MacOS last August, the python ports are reporting a
dependency on either openssl11 or openssl3, neither of which are to be found in
the (local?) index for MacPorts, according to the error I have received, copied
below. While I am prompted to report a bug, I presume I
ng-importerror.html
:info:build Please note and check the following:
:info:build * The Python version is: Python3.9 from
"/opt/local/Library/Frameworks/Python.framework/Versions/3.9/bin/python3.9"
:info:build * The NumPy version is: "1.21.2"
:info:build and make sure that they
ly adding 39 to
>
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python/py-matplotlib-basemap/Portfile
>
> does not automagically allow to try
>
> sudo port install py39-matplotlib-basemap (Error: Port
> py39-matplotlib-basemap not found)
&
Ok, thanks anyway for the not-so-good news… ;-)
But out of curiosity, from my experiments I learned that simply adding 39 to
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python/py-matplotlib-basemap/Portfile
does not automagically allow to try
sudo port
er supported in Python 3.9. There is no easy workaround to this.
Marius
--
Marius Schamschula
> On Oct 14, 2021, at 7:31 AM, VACCARI FRANCO wrote:
>
> Hi,
>
> I’m going to experiment with python on a new M1 MacMini and installed
> python39 and most of the package
Hi,
I’m going to experiment with python on a new M1 MacMini and installed python39
and most of the packages needed by instaseis
<https://instaseis.net>
I’m getting in trouble with matplotlib-basemap. I see several versions listed
but not the one for python39. If I look at the versi
1 - 100 of 233 matches
Mail list logo
