Re: building seamonkey - python setup - imp module

[Riccardo Mottola via macports-users]

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 other code which is 
more complicated, different issue though.


Thanks for the quick answer.

-Ric

Re: building seamonkey - python setup - imp module

[Nils Breunese]

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) [Clang 15.0.0 
(clang-1500.1.0.2.5)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import imp
:1: DeprecationWarning: the imp module is deprecated in favour of 
importlib and slated for removal in Python 3.12; see the module's documentation 
for alternative uses

But it is indeed no longer present in Python 3.12:

❯ /opt/local/bin/python3.12Python 3.12.6 (main, Sep  7 2024, 05:15:33) 
[Clang 15.0.0 (clang-1500.1.0.2.5)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import imp
Traceback (most recent call last):
  File "", line 1, in 
ModuleNotFoundError: No module named ‘imp'

I guess you’ll either need to use an older Python version, or patch SeaMonkey 
to use the importlib module instead.

Nils.

Riccardo Mottola via macports-users  wrote:

> Hi,
> 
> I would like to try to build SeaMonkey on 10.9 Mavericks. A decent browser 
> and a good email client. Officially not supported on 10.9, but it works on 
> 10.11, so I have some hope it can be convinced to run. Maybe some of you want 
> to help?
> 
> Biggest issue is getting it to run. Latest version 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
> Python 3.12.6
> 
> but when I run I get:
> /Users/multix/code/seamonkey-2.53.19/./mach:12: SyntaxWarning: invalid escape 
> sequence '\ '
>  ''':'
> Traceback (most recent call last):
>  File "/Users/multix/code/seamonkey-2.53.19/./mach", line 270, in 
>main(sys.argv[1:])
>  File "/Users/multix/code/seamonkey-2.53.19/./mach", line 262, in main
>mach = get_mach()
>   ^^
>  File "/Users/multix/code/seamonkey-2.53.19/./mach", line 252, in get_mach
>mach = check_and_get_mach(dir_path)
>   
>  File "/Users/multix/code/seamonkey-2.53.19/./mach", line 208, in 
> check_and_get_mach
>return load_mach(dir_path, mach_path)
>   ^^
>  File "/Users/multix/code/seamonkey-2.53.19/./mach", line 196, in load_mach
>return mach_bootstrap.bootstrap(dir_path)
>   ^^
>  File "/Users/multix/code/seamonkey-2.53.19/build/mach_bootstrap.py", line 
> 189, in bootstrap
>import mach.main
>  File "/Users/multix/code/seamonkey-2.53.19/python/mach/mach/main.py", line 
> 13, in 
>import imp
> ModuleNotFoundError: No module named 'imp'
> 
> I understand it is not finding module “imp”. I wonder if my python 3.12 
> misses some module to isntall? any python expert here?
> 
> Riccardo
> 
> -- 
> Sent with GNUMail on MacBook Pro running Mavericks
> 

Re: building seamonkey - python setup - imp module

[Bill Cole]

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 expert. I could not write "Hello World" in python without 
cribbing...

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.



-- 
Bill Cole

building seamonkey - python setup - imp module

[Riccardo Mottola via macports-users]

Hi,

I would like to try to build SeaMonkey on 10.9 Mavericks. A decent browser and 
a good email client. Officially not supported on 10.9, but it works on 10.11, 
so I have some hope it can be convinced to run. Maybe some of you want to help?

Biggest issue is getting it to run. Latest version 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
Python 3.12.6

but when I run I get:
/Users/multix/code/seamonkey-2.53.19/./mach:12: SyntaxWarning: invalid escape 
sequence '\ '
  ''':'
Traceback (most recent call last):
  File "/Users/multix/code/seamonkey-2.53.19/./mach", line 270, in 
main(sys.argv[1:])
  File "/Users/multix/code/seamonkey-2.53.19/./mach", line 262, in main
mach = get_mach()
   ^^
  File "/Users/multix/code/seamonkey-2.53.19/./mach", line 252, in get_mach
mach = check_and_get_mach(dir_path)
   
  File "/Users/multix/code/seamonkey-2.53.19/./mach", line 208, in 
check_and_get_mach
return load_mach(dir_path, mach_path)
   ^^
  File "/Users/multix/code/seamonkey-2.53.19/./mach", line 196, in load_mach
return mach_bootstrap.bootstrap(dir_path)
   ^^
  File "/Users/multix/code/seamonkey-2.53.19/build/mach_bootstrap.py", line 
189, in bootstrap
import mach.main
  File "/Users/multix/code/seamonkey-2.53.19/python/mach/mach/main.py", line 
13, in 
import imp
ModuleNotFoundError: No module named 'imp'

I understand it is not finding module “imp”. I wonder if my python 3.12 misses 
some module to isntall? any python expert here?

Riccardo

-- 
Sent with GNUMail on MacBook Pro running Mavericks

Re: Any alternative strategies to limit the proliferation of perl and python packages?

[raf via macports-users]

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 them and figure out which old
> ones I can throw out". MAYBE that would be easier if I kept my entire
> installation perfectly up to date, but I have my doubts.
> 
> I just did some quick testing with Python3 and as I thought it's
> possible to *append* the site-packages directories of older 3.x
> versions to the sys.path and get access to anything already installed
> there. Perl is alienware for me but I would be surprised if it didn't
> support a similar trick. IIRC both allow to define the default search
> path via a configuration file, and python at least doesn't complain
> about non-existing directories on that path.
> 
> Wouldn't that at least allow for a non-invasive design (= that doesn't
> break everything) to relax the Perl/Python upgrade requirements for
> ports that have build dependencies on one or both of those, and maybe
> even those that do not install their own binary P/P extensions (= any
> runtime dependencies go through the standalone interpreter)? It'd be
> great if those ports could just depend on port:perl5/port:python3 (the
> latter doesn't but could exist?!) and p5-foo/py-foo ports, and be
> happy with whatever is currently present. That aspect already works
> with perl5 (but I haven't tested it by making a newer perl version use
> packages/pods installed for a previous version).
> 
> R.

I assume that you're referring to perl modules that were installed "manually"
via CPAN rather than via macports. They need to be reinstalled for new versions
of perl. I think the usual solution to this is to install them into a directory
that isn't perl-version-specific.

For example, if perl -V shows this:

  @INC:
/opt/local/lib/perl5/site_perl/5.34/darwin-thread-multi-2level
/opt/local/lib/perl5/site_perl/5.34
/opt/local/lib/perl5/vendor_perl/5.34/darwin-thread-multi-2level
/opt/local/lib/perl5/vendor_perl/5.34
/opt/local/lib/perl5/5.34/darwin-thread-multi-2level
/opt/local/lib/perl5/5.34

They are all perl version specific, so you could add another directory
to PERL5LIB:

  PERL5LIB=/usr/local/lib/site_perl

Then cpan modules could be installed into /usr/local/lib/site_perl.
Then they would remain available across perl upgrades.

I'm not sure how to make that happen. It presumably depends on which CPAN
client you use. According to 
https://stackoverflow.com/questions/51880115/install-with-cpan-perl-modules-to-specific-directory-when-several-appear-in-us
here are the cpan commands to make it happen.

  o conf makepl_arg 'PREFIX=/usr/local/lib/site_perl 
INSTALLMAN3DIR=/usr/local/lib/site_perl/man/man3'
  o conf mbuild_arg '--install_base /usr/local/lib/site_perl'
  o conf mbuild_install_arg '--install_base /usr/local/lib/site_perl'
  o conf mbuildpl_arg '--install-base /usr/local/lib/site_perl'
  [o conf commit]

However, I don't think it would help for modules that require compiling C. I
have a site that requires some CPAN cryptography modules, and just using the
same files isn't enough. They had to be recompiled to match the new perl
version. But it should be mostly fine for pure perl modules.

For python, using virtual environments are recommended, which would address
this, and hopefully they've found a way by now for them to not make it
difficult to run a python program from the command line.

Another option is to create and submit Portfiles for all of the modules that
you use. Then macports should take care of everything. :-)

cheers,
raf

Any alternative strategies to limit the proliferation of perl and python packages?

[René J . V . Bertin]

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 entire installation perfectly up to date, but 
I have my doubts.

I just did some quick testing with Python3 and as I thought it's possible to 
*append* the site-packages directories of older 3.x versions to the sys.path 
and get access to anything already installed there. Perl is alienware for me 
but I would be surprised if it didn't support a similar trick. IIRC both allow 
to define the default search path via a configuration file, and python at least 
doesn't complain about non-existing directories on that path.

Wouldn't that at least allow for a non-invasive design (= that doesn't break 
everything) to relax the Perl/Python upgrade requirements for ports that have 
build dependencies on one or both of those, and maybe even those that do not 
install their own binary P/P extensions (= any runtime dependencies go through 
the standalone interpreter)? It'd be great if those ports could just depend on 
port:perl5/port:python3 (the latter doesn't but could exist?!) and 
p5-foo/py-foo ports, and be happy with whatever is currently present. That 
aspect already works with perl5 (but I haven't tested it by making a newer perl 
version use packages/pods installed for a previous version).

R.

Re: Python and python3

[ideal . cat9953]

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 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 wrong (in this case, system) python.
>
> You can control both the python and python3 symlinks in the prefix with
> the 'port select' action, for example:
>
>   sudo port select --set python python312
>   sudo port select --set python3 python312

Ahhh, the only usage I saw was just python, I didn’t realize you could do both. 
Very good, thank you!

Re: Python and python3

[Rainer Müller]

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 habit to switch after so many years, and I don’t want to
> accidentally use the wrong (in this case, system) python.

You can control both the python and python3 symlinks in the prefix with
the 'port select' action, for example:

  sudo port select --set python python312
  sudo port select --set python3 python312

Rainer

Python and python3

[ideal . cat9953]

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 wrong (in this case, 
system) python.

Re: Borg backup is complaining about msgpack python package version

[Kenneth Wolcott]

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 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
>
> port installed | grep msgpack
>   msgpack @4_0 (active)
>   msgpack-c @4.0.0_0
>   msgpack-c @6.0.0_0 (active)
>   msgpack-cpp @4.1.1_0
>   msgpack-cpp @6.0.0_0
>   msgpack-cpp @6.1.0_0 (active)
>   py312-msgpack @1.0.7_1
>   py312-msgpack @1.0.8_0 (active)
>
> port installed | grep borgbackup
>   borgbackup @1.2.7_0 (active)
>
>   Do I need to re-activate the prior version of py312-msgpack?
>
>   Is there a way to prevent this going forwards?
>
> Thanks,
> Ken Wolcott
>
> On Fri, Jan 5, 2024 at 6:11 AM Joshua Root  wrote:
> >
> > 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 it
> > > should start working again.
> >
> > Yes, updating to 1.2.7 was the resolution to the ticket that was opened
> > about this. <https://trac.macports.org/ticket/68998>
> >
> > - Josh

Re: Borg backup is complaining about msgpack python package version

[Kenneth Wolcott]

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 status, rc 2

port installed | grep msgpack
  msgpack @4_0 (active)
  msgpack-c @4.0.0_0
  msgpack-c @6.0.0_0 (active)
  msgpack-cpp @4.1.1_0
  msgpack-cpp @6.0.0_0
  msgpack-cpp @6.1.0_0 (active)
  py312-msgpack @1.0.7_1
  py312-msgpack @1.0.8_0 (active)

port installed | grep borgbackup
  borgbackup @1.2.7_0 (active)

  Do I need to re-activate the prior version of py312-msgpack?

  Is there a way to prevent this going forwards?

Thanks,
Ken Wolcott

On Fri, Jan 5, 2024 at 6:11 AM Joshua Root  wrote:
>
> 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 it
> > should start working again.
>
> Yes, updating to 1.2.7 was the resolution to the ticket that was opened
> about this. <https://trac.macports.org/ticket/68998>
>
> - Josh

Re: Borg backup is complaining about msgpack python package version

[Joshua Root]

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 it
should start working again.


Yes, updating to 1.2.7 was the resolution to the ticket that was opened 
about this. 


- Josh

Re: Borg backup is complaining about msgpack python package version

[Joshua Root]

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 very 
poor backward compatibility practices. Interfaces change in incompatible 
ways all the time, often without the compatibility break being 
documented. I would assume a past minor version increase of msgpack 
broke borgbackup, which created a support burden for them, so now they 
pin the version.


This is bad for basically everyone, because client projects stick with 
old versions with old bugs out of caution even when newer ones would 
work fine (as in this case), it creates extra work when they do update, 
and it's really easy to get into situations with diamond dependencies 
where conflicting versions of the same module are required. This one 
issue is largely responsible for the need to have a separate venv for 
every project, each with identical or only slightly different copies of 
many of the dependencies.


And unfortunately, this is a social issue with no easy fix. :(

- Josh

Re: Borg backup is complaining about msgpack python package version

[Clemens Lang]

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 specific, supported versions are required
> > by our setup.py.
> > Do not contact borgbackup support about this.
> > terminating with error status, rc 2
> 
> 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.
> 
> jmr committed the last update to msgpack in
>   
> https://github.com/macports/macports-ports/commit/0dce65698d178a176c0984859080d6ff9da07fe8
> 
> The upstream change to allow msgpack 1.0.7 is
>   
> https://github.com/borgbackup/borg/commit/cdcab4df6851b5d3da6ac5435bcaeb8aa1d632b5
> 
> You'll notice that this change does not come with any modifications of
> the source code otherwise, so msgpack 1.0.7 would work with your
> existing version of borgbackup, but it refuses it for no good reason.
> 
> This upstream commit is not in a tagged release yet, so we need to
> backport it manually to borgbackup.

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 it
should start working again.

-- 
Clemens

Re: Borg backup is complaining about msgpack python package version

[Clemens Lang]

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 borgbackup support about this.
> terminating with error status, rc 2

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.

jmr committed the last update to msgpack in
  
https://github.com/macports/macports-ports/commit/0dce65698d178a176c0984859080d6ff9da07fe8

The upstream change to allow msgpack 1.0.7 is
  
https://github.com/borgbackup/borg/commit/cdcab4df6851b5d3da6ac5435bcaeb8aa1d632b5

You'll notice that this change does not come with any modifications of
the source code otherwise, so msgpack 1.0.7 would work with your
existing version of borgbackup, but it refuses it for no good reason.

This upstream commit is not in a tagged release yet, so we need to
backport it manually to borgbackup.

-- 
Clemens

Re: How to wean myself away from Python 3.9? and then Python3.10?

[raf via macports-users]

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 and then
> Python 3.9 and then re-install those apps that I uninstalled from the
> first sequence?  How will that not put me back to where O started?

I don't think you need to think about it. Python-based
ports tend to just depend on whatever is macports's
current default python port which gets updated
annually. A handful (38 out of 2261) declare a specific
default python version. When there are no longer any
ports depending on an old version of python, it
probably automatically becomes a candidate for removal
unless it was explicitly requested.

> The same question applies to Perl.

Perl-based ports are slightly different. They tend to
declare a range of perl5 versions that they work with
(usually the four that are supported at any time by
macports).

I think if you regularly selfupdate and upgrade outdated and
reclaim, it'll probably look after itself. At least, that's my
mental model. Corrections are always welcome.

> Thanks,
> Ken Wolcott

cheers,
raf

Re: How to wean myself away from Python 3.9? and then Python3.10?

[Steven Smith]

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 "py${OLDV}-*"

> On Dec 31, 2023, at 04:47, 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 and then
> Python 3.9 and then re-install those apps that I uninstalled from the
> first sequence?  How will that not put me back to where O started?
> 
> The same question applies to Perl.
> 
> Thanks,
> Ken Wolcott

How to wean myself away from Python 3.9? and then Python3.10?

[Kenneth Wolcott]

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 will that not put me back to where O started?

The same question applies to Perl.

Thanks,
Ken Wolcott

Re: Borg backup is complaining about msgpack python package version

[Kenneth Wolcott]

port installed | grep msgpack
  msgpack @4_0 (active)
  msgpack-c @4.0.0_0
  msgpack-c @6.0.0_0 (active)
  msgpack-cpp @4.1.1_0
  msgpack-cpp @6.0.0_0
  msgpack-cpp @6.1.0_0 (active)
  py310-msgpack @1.0.4_2
  py310-msgpack @1.0.5_0
  py310-msgpack @1.0.7_0 (active)
~: port installed | grep 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 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

Borg backup is complaining about msgpack python package version

[Kenneth Wolcott]

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

Re: Should I install Anaconda (or miniconda) Python?

[Tao Zhang]

  I have to use "source .cshrc" to change back to previous state.
  Although I delete all sentences in .bash_profile, it still comes with 
anaconda environments when I start a new terminal.

 Weird!

On 4/29/23 10:46 AM, Tao Zhang wrote:


 My .cshrc file is not changed. The only changed file is .bash_profile 
(see 3).

 When I start a new terminal, it comes with anaconda environments.

 So maybe I have to comment the .bash_profile?
 Do you use .cshrc or .bashrc file?
 Do those "the code between >>> conda initialize and <<<< conda 
initialize" appear in  your .cshrc or .bashrc file or other file?


 Thanks
 Tao

On 4/29/23 10:36 AM, Balthasar Indermuehle wrote:

That's odd. The same procedure works fine for me.

Maybe try this:
Remove or comment the code between >>> conda initialize 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 
before. Where does /opt/local/bin/python3 point?




Dr Balthasar Indermühle
Inside Systems Pty Ltd
5007/101 Bathurst Street
Sydney NSW 2000, Australia
t: +61 (0)405 988 500



On Sun, 30 Apr 2023 at 02:27, Tao Zhang  wrote:

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
not work (see 4)

 How can I return to previous state in which .cshrc and
associated command can work if I do not uninstall the Anaconda
python?

 Thanks
 Tao


1) [MacBook-Pro:~] tzhang% python3
python3: Command not found.


2) my .cshrc file
"setenv PATH /usr/local/bin:/opt/local/bin:/opt/local/sbin:$PATH"

3)  .bash_profile  after installing Anaconda python
-
# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
__conda_setup="$('/Users/tzhang/anaconda3/bin/conda' 'shell.bash'
'hook' 2> /dev/null)"
if [ $? -eq 0 ]; then
    eval "$__conda_setup"
else
    if [ -f "/Users/tzhang/anaconda3/etc/profile.d/conda.sh" ]; then
    . "/Users/tzhang/anaconda3/etc/profile.d/conda.sh"
    else
    export PATH="/Users/tzhang/anaconda3/bin:$PATH"
    fi
fi
unset __conda_setup
# <<< conda initialize <<<
---

4)
[MacBook-Pro:~] tzhang% conda deactivate
[MacBook-Pro:~] tzhang% python3
python3: Command not found.



On 4/28/23 6:57 PM, Balthasar Indermuehle wrote:

The same, so long as your anaconda environment is activated.
Type conda activate  to activate

On Sat, 29 Apr 2023 at 10:49, Tao Zhang 
wrote:

Hi Balthasar,

  Thanks for your helpful info.

  For now, I am using  "python3 filename.py" to run python
code in Mac terminal.
  I am asking what's the new command to run python code with
Anaconda in the terminal?
  Thanks
  Tao


On 4/28/23 6:30 PM, Balthasar Indermuehle wrote:

Anaconda/miniconda install themselves into a completely
separate directory.

On installing, it'll offer to add itself to the startup
scripts so when you open a terminal, it will automatically
load the anaconda/miniconda environment. type "conda
deactivate" to exit from that if you want to use your other
local python install.

I personally found myself moving towards anaconda
immediately after installing it for the first time. Removes
a huge headache of package compatibility issues. Just
create a new environment if you need to use a package that
doesn't play nice with others.


On Sat, 29 Apr 2023 at 10:13, Tao Zhang
 wrote:

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 Python conflict with the
installed Macport python?

  Thanks

  Tao

  /Users/tzhang> which python3
/opt/local/bin/python3
/Users/tzhang> python3
Python 3.9.1 (default, Dec  8 2020, 11:52:28)
[Clang 10.0.1 (clan

Re: Should I install Anaconda (or miniconda) Python?

[Tao Zhang]

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 3).

 When I start a new terminal, it comes with anaconda environments.

 So maybe I have to comment the .bash_profile?
 Do you use .cshrc or .bashrc file?
 Do those "the code between >>> conda initialize and <<<< conda 
initialize" appear in  your .cshrc or .bashrc file or other file?


 Thanks
 Tao

On 4/29/23 10:36 AM, Balthasar Indermuehle wrote:

That's odd. The same procedure works fine for me.

Maybe try this:
Remove or comment the code between >>> conda initialize 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 
before. Where does /opt/local/bin/python3 point?




Dr Balthasar Indermühle
Inside Systems Pty Ltd
5007/101 Bathurst Street
Sydney NSW 2000, Australia
t: +61 (0)405 988 500



On Sun, 30 Apr 2023 at 02:27, Tao Zhang  wrote:

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
not work (see 4)

 How can I return to previous state in which .cshrc and
associated command can work if I do not uninstall the Anaconda
python?

 Thanks
 Tao


1) [MacBook-Pro:~] tzhang% python3
python3: Command not found.


2) my .cshrc file
"setenv PATH /usr/local/bin:/opt/local/bin:/opt/local/sbin:$PATH"

3)  .bash_profile  after installing Anaconda python
-
# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
__conda_setup="$('/Users/tzhang/anaconda3/bin/conda' 'shell.bash'
'hook' 2> /dev/null)"
if [ $? -eq 0 ]; then
    eval "$__conda_setup"
else
    if [ -f "/Users/tzhang/anaconda3/etc/profile.d/conda.sh" ]; then
    . "/Users/tzhang/anaconda3/etc/profile.d/conda.sh"
    else
    export PATH="/Users/tzhang/anaconda3/bin:$PATH"
    fi
fi
unset __conda_setup
# <<< conda initialize <<<
---

4)
[MacBook-Pro:~] tzhang% conda deactivate
[MacBook-Pro:~] tzhang% python3
python3: Command not found.



On 4/28/23 6:57 PM, Balthasar Indermuehle wrote:

The same, so long as your anaconda environment is activated.
Type conda activate  to activate

On Sat, 29 Apr 2023 at 10:49, Tao Zhang 
wrote:

Hi Balthasar,

  Thanks for your helpful info.

  For now, I am using  "python3 filename.py" to run python
code in Mac terminal.
  I am asking what's the new command to run python code with
Anaconda in the terminal?
  Thanks
  Tao


On 4/28/23 6:30 PM, Balthasar Indermuehle wrote:

Anaconda/miniconda install themselves into a completely
separate directory.

On installing, it'll offer to add itself to the startup
scripts so when you open a terminal, it will automatically
load the anaconda/miniconda environment. type "conda
deactivate" to exit from that if you want to use your other
local python install.

I personally found myself moving towards anaconda
immediately after installing it for the first time. Removes
a huge headache of package compatibility issues. Just
create a new environment if you need to use a package that
doesn't play nice with others.


On Sat, 29 Apr 2023 at 10:13, Tao Zhang
 wrote:

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 Python conflict with the
installed Macport python?

  Thanks

  Tao

  /Users/tzhang> which python3
/opt/local/bin/python3
/Users/tzhang> python3
Python 3.9.1 (default, Dec  8 2020, 11:52:28)
[Clang 10.0.1 (clang-1001.0.46.4)] on darwin
   

Re: Should I install Anaconda (or miniconda) Python?

[Tao Zhang]

 My .cshrc file is not changed. The only changed file is .bash_profile 
(see 3).

 When I start a new terminal, it comes with anaconda environments.

 So maybe I have to comment the .bash_profile?
 Do you use .cshrc or .bashrc file?
 Do those "the code between >>> conda initialize and <<<< conda 
initialize" appear in  your .cshrc or .bashrc file or other file?


 Thanks
 Tao

On 4/29/23 10:36 AM, Balthasar Indermuehle wrote:

That's odd. The same procedure works fine for me.

Maybe try this:
Remove or comment the code between >>> conda initialize 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 before. 
Where does /opt/local/bin/python3 point?




Dr Balthasar Indermühle
Inside Systems Pty Ltd
5007/101 Bathurst Street
Sydney NSW 2000, Australia
t: +61 (0)405 988 500



On Sun, 30 Apr 2023 at 02:27, Tao Zhang  wrote:

    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 not
work (see 4)

 How can I return to previous state in which .cshrc and associated
command can work if I do not uninstall the Anaconda python?

 Thanks
 Tao


1) [MacBook-Pro:~] tzhang% python3
python3: Command not found.


2) my .cshrc file
"setenv PATH /usr/local/bin:/opt/local/bin:/opt/local/sbin:$PATH"

3)  .bash_profile  after installing Anaconda python
-
# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
__conda_setup="$('/Users/tzhang/anaconda3/bin/conda' 'shell.bash'
'hook' 2> /dev/null)"
if [ $? -eq 0 ]; then
    eval "$__conda_setup"
else
    if [ -f "/Users/tzhang/anaconda3/etc/profile.d/conda.sh" ]; then
    . "/Users/tzhang/anaconda3/etc/profile.d/conda.sh"
    else
    export PATH="/Users/tzhang/anaconda3/bin:$PATH"
    fi
fi
unset __conda_setup
# <<< conda initialize <<<
---

4)
[MacBook-Pro:~] tzhang% conda deactivate
[MacBook-Pro:~] tzhang% python3
python3: Command not found.



On 4/28/23 6:57 PM, Balthasar Indermuehle wrote:

The same, so long as your anaconda environment is activated. Type
conda activate  to activate

On Sat, 29 Apr 2023 at 10:49, Tao Zhang 
wrote:

Hi Balthasar,

  Thanks for your helpful info.

  For now, I am using  "python3 filename.py" to run python
code in Mac terminal.
  I am asking what's the new command to run python code with
Anaconda in the terminal?
  Thanks
  Tao


On 4/28/23 6:30 PM, Balthasar Indermuehle wrote:

Anaconda/miniconda install themselves into a completely
separate directory.

On installing, it'll offer to add itself to the startup
scripts so when you open a terminal, it will automatically
load the anaconda/miniconda environment. type "conda
deactivate" to exit from that if you want to use your other
local python install.

I personally found myself moving towards anaconda
immediately after installing it for the first time. Removes
a huge headache of package compatibility issues. Just create
a new environment if you need to use a package that doesn't
play nice with others.


On Sat, 29 Apr 2023 at 10:13, Tao Zhang
 wrote:

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 Python conflict with the installed
Macport python?

  Thanks

  Tao

  /Users/tzhang> which python3
/opt/local/bin/python3
/Users/tzhang> python3
Python 3.9.1 (default, Dec  8 2020, 11:52:28)
[Clang 10.0.1 (clang-1001.0.46.4)] on darwin
Type "help", "copyright", "credits" or "license" for
more information.
 >>>

-

commands.

Re: Should I install Anaconda (or miniconda) Python?

[Tao Zhang]

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 not work 
(see 4)


 How can I return to previous state in which .cshrc and associated 
command can work if I do not uninstall the Anaconda python?


 Thanks
 Tao


1) [MacBook-Pro:~] tzhang% python3
python3: Command not found.


2) my .cshrc file
"setenv PATH /usr/local/bin:/opt/local/bin:/opt/local/sbin:$PATH"

3)  .bash_profile  after installing Anaconda python
-
# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
__conda_setup="$('/Users/tzhang/anaconda3/bin/conda' 'shell.bash' 'hook' 
2> /dev/null)"

if [ $? -eq 0 ]; then
    eval "$__conda_setup"
else
    if [ -f "/Users/tzhang/anaconda3/etc/profile.d/conda.sh" ]; then
    . "/Users/tzhang/anaconda3/etc/profile.d/conda.sh"
    else
    export PATH="/Users/tzhang/anaconda3/bin:$PATH"
    fi
fi
unset __conda_setup
# <<< conda initialize <<<
---

4)
[MacBook-Pro:~] tzhang% conda deactivate
[MacBook-Pro:~] tzhang% python3
python3: Command not found.



On 4/28/23 6:57 PM, Balthasar Indermuehle wrote:
The same, so long as your anaconda environment is activated. Type 
conda activate  to activate


On Sat, 29 Apr 2023 at 10:49, Tao Zhang  wrote:

Hi Balthasar,

  Thanks for your helpful info.

  For now, I am using  "python3 filename.py" to run python code in
Mac terminal.
  I am asking what's the new command to run python code with
Anaconda in the terminal?
  Thanks
  Tao


On 4/28/23 6:30 PM, Balthasar Indermuehle wrote:

Anaconda/miniconda install themselves into a completely separate
directory.

On installing, it'll offer to add itself to the startup scripts
so when you open a terminal, it will automatically load the
anaconda/miniconda environment. type "conda deactivate" to exit
from that if you want to use your other local python install.

I personally found myself moving towards anaconda immediately
after installing it for the first time. Removes a huge headache
of package compatibility issues. Just create a new environment if
you need to use a package that doesn't play nice with others.


On Sat, 29 Apr 2023 at 10:13, Tao Zhang 
wrote:

    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 Python conflict with the installed
Macport python?

  Thanks

  Tao

  /Users/tzhang> which python3
/opt/local/bin/python3
/Users/tzhang> python3
Python 3.9.1 (default, Dec  8 2020, 11:52:28)
[Clang 10.0.1 (clang-1001.0.46.4)] on darwin
Type "help", "copyright", "credits" or "license" for more
information.
 >>>

-

commands.
9:00 - 10:00
Office hours by appointment: Python/Anaconda Troubleshooting
and Assistance
10:00 - 10:05 (5 min)
Welcome and opening remarks
Topic
Application/Package(s)
10:05 - 10:45
(40 mins)
Topic 1: Getting Started with Python and Jupyter Notebooks
Jupyter Notebook
NumPy
Pandas

Notes:
• This tutorial is hands on, you will need to have Anaconda (or
miniconda) Python installed on your computer prior to the
workshop

Install Python via Anaconda
Install the latest version of Anaconda on your local machine
for this
tutorial.
Need help installing Anaconda? Video tutorial on YouTube.
Note: some of
the packages in the video might not apply to this workshop.
Use the list
below.
Additional packages: Install the following extra package for
Python by
going to Start  Anaconda3  Anaconda Prompt (PC Users) or
the terminal
(Mac/Linux users) and type:
conda install -c conda-forge cartopy
conda install -c conda-forge h5netcdf
conda install -c conda-forge xarray
conda install -c conda-forge s3fs

Check if the install is successful
Launch Jupyter Notebooks from the Anaconda Navigator
• PC Users: Go to Start  Anaconda3  Jupyter Notebook
• Mac/Linux Users: Type Jupyter notebook into the terminal

---



--

Dr Balthasar Indermühle
Inside Systems Pty Ltd
5007/101 Bathurst Street
Sydney NSW 2000, Australia
t: +61 (0)405 988 500

Re: Should I install Anaconda (or miniconda) Python?

[Tao Zhang]

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 install -c conda-forge s3fs



On 4/29/23 5:02 AM, Marius Schamschula wrote:

All of the packages listed are also available in MacPorts.

Packages installed by anaconda and pip need to be separately maintained, and 
will cause conflicts.

Whenever I run into instructions that require anaconda, I usually create new 
ports for any missing packages.


On Apr 28, 2023, at 7:13 PM, Tao Zhang  wrote:

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 Python conflict with the installed Macport python?

  Thanks

  Tao

  /Users/tzhang> which python3
/opt/local/bin/python3
/Users/tzhang> python3
Python 3.9.1 (default, Dec  8 2020, 11:52:28)
[Clang 10.0.1 (clang-1001.0.46.4)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
-

commands.
9:00 - 10:00
Office hours by appointment: Python/Anaconda Troubleshooting and Assistance
10:00 - 10:05 (5 min)
Welcome and opening remarks
Topic
Application/Package(s)
10:05 - 10:45
(40 mins)
Topic 1: Getting Started with Python and Jupyter Notebooks
Jupyter Notebook
NumPy
Pandas

Notes:
• This tutorial is hands on, you will need to have Anaconda (or miniconda) 
Python installed on your computer prior to the workshop

Install Python via Anaconda
Install the latest version of Anaconda on your local machine for this tutorial.
Need help installing Anaconda? Video tutorial on YouTube. Note: some of the 
packages in the video might not apply to this workshop. Use the list below.
Additional packages: Install the following extra package for Python by going to 
Start  Anaconda3  Anaconda Prompt (PC Users) or the terminal (Mac/Linux 
users) and type:
conda install -c conda-forge cartopy
conda install -c conda-forge h5netcdf
conda install -c conda-forge xarray
conda install -c conda-forge s3fs

Check if the install is successful
Launch Jupyter Notebooks from the Anaconda Navigator
• PC Users: Go to Start  Anaconda3  Jupyter Notebook
• Mac/Linux Users: Type Jupyter notebook into the terminal

---

Re: Should I install Anaconda (or miniconda) Python?

[akierig]

Hi Tao:

As a Librarian who sometimes helps with workshops like these I am really 
happy to see you asking about this.


It would probably conflict but there are workarounds!

My suggestion would be to install it but remove it from your `PATH` (in 
your `.bashrc` or similar). On the day  of the 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 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 Python conflict with the installed Macport 
python?


 Thanks

 Tao

 /Users/tzhang> which python3
/opt/local/bin/python3
/Users/tzhang> python3
Python 3.9.1 (default, Dec  8 2020, 11:52:28)
[Clang 10.0.1 (clang-1001.0.46.4)] on darwin
Type "help", "copyright", "credits" or "license" for more information.




-

commands.
9:00 - 10:00
Office hours by appointment: Python/Anaconda Troubleshooting and 
Assistance

10:00 - 10:05 (5 min)
Welcome and opening remarks
Topic
Application/Package(s)
10:05 - 10:45
(40 mins)
Topic 1: Getting Started with Python and Jupyter Notebooks
Jupyter Notebook
NumPy
Pandas

Notes:
• This tutorial is hands on, you will need to have Anaconda (or 
miniconda) Python installed on your computer prior to the workshop


Install Python via Anaconda
Install the latest version of Anaconda on your local machine for this 
tutorial.
Need help installing Anaconda? Video tutorial on YouTube. Note: some 
of the packages in the video might not apply to this workshop. Use the 
list below.
Additional packages: Install the following extra package for Python by 
going to Start  Anaconda3  Anaconda Prompt (PC Users) or the 
terminal (Mac/Linux users) and type:

conda install -c conda-forge cartopy
conda install -c conda-forge h5netcdf
conda install -c conda-forge xarray
conda install -c conda-forge s3fs

Check if the install is successful
Launch Jupyter Notebooks from the Anaconda Navigator
• PC Users: Go to Start  Anaconda3  Jupyter Notebook
• Mac/Linux Users: Type Jupyter notebook into the terminal

---

Should I install Anaconda (or miniconda) Python?

[Tao Zhang]

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 Python conflict with the installed Macport python?

 Thanks

 Tao

 /Users/tzhang> which python3
/opt/local/bin/python3
/Users/tzhang> python3
Python 3.9.1 (default, Dec  8 2020, 11:52:28)
[Clang 10.0.1 (clang-1001.0.46.4)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>>

-

commands.
9:00 - 10:00
Office hours by appointment: Python/Anaconda Troubleshooting and Assistance
10:00 - 10:05 (5 min)
Welcome and opening remarks
Topic
Application/Package(s)
10:05 - 10:45
(40 mins)
Topic 1: Getting Started with Python and Jupyter Notebooks
Jupyter Notebook
NumPy
Pandas

Notes:
• This tutorial is hands on, you will need to have Anaconda (or 
miniconda) Python installed on your computer prior to the workshop


Install Python via Anaconda
Install the latest version of Anaconda on your local machine for this 
tutorial.
Need help installing Anaconda? Video tutorial on YouTube. Note: some of 
the packages in the video might not apply to this workshop. Use the list 
below.
Additional packages: Install the following extra package for Python by 
going to Start  Anaconda3  Anaconda Prompt (PC Users) or the terminal 
(Mac/Linux users) and type:

conda install -c conda-forge cartopy
conda install -c conda-forge h5netcdf
conda install -c conda-forge xarray
conda install -c conda-forge s3fs

Check if the install is successful
Launch Jupyter Notebooks from the Anaconda Navigator
• PC Users: Go to Start  Anaconda3  Jupyter Notebook
• Mac/Linux Users: Type Jupyter notebook into the terminal

---

ipython Problem (suspected python select or vt100)

[Eckard Brauer]

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.

Putting  a debug print  statement to the bottom function, it shows up
that it's on the 3rd call of selectors.KqueueSelector.register(),

Is that either a known problem or could any kind person provide some
helpful hints to solve that?

Thanks in advance,
Eckard


- snip! -
...
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.11/
lib/python3.11/site-packages/prompt_toolkit/application/
application.py", line 737, in _run_async
with self.input.raw_mode(), self.input.attach(
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.11/
lib/python3.11/contextlib.py", line 137, in __enter__
return next(self.gen)
   ^^
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.11/
lib/python3.11/site-packages/prompt_toolkit/input/vt100.py", line 176,
in _attached_input
loop.add_reader(fd, callback_wrapper)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.11/
lib/python3.11/asyncio/selector_events.py", line 340, in add_reader
self._add_reader(fd, callback, *args)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.11/
lib/python3.11/asyncio/selector_events.py", line 267, in _add_reader
self._selector.register(fd, selectors.EVENT_READ,
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.11/
lib/python3.11/selectors.py", line 522, in register
self._selector.control([kev], 0, 0)
OSError: [Errno 45] Operation not supported

If you suspect this is an IPython 8.8.0 bug, please report it at:
https://github.com/ipython/ipython/issues
or send an email to the mailing list at ipython-...@python.org

You can print a more detailed traceback right now with "%tb", or use
"%debug"
to interactively debug it.

Extra-detailed tracebacks for bug-reporting purposes can be enabled via:
%config Application.verbose_crash=True
- snipsnap! -
*** DEBUG: KqueueSelector.register(self, fileobj, events, data) =
(, 0, 1, (.callback_wrapper() at /opt/local/Library/
Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/
prompt_toolkit/input/vt100.py:165>, None))
- snap! -

meld (gtk + python) developed display glitches on High Sierra

[Riccardo Mottola via macports-users]

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 are shown. 
Several entries do not traw, are blank, sometimes passing over with a 
mouse shows them, sometimes not.


My first attempt would be to revert some port to an older version, I 
checked with "port installed" and don't find many. A hint on what could 
be causing this?
First culprit would be gtk3, but I have only one recent version, same is 
for gtk2, harfbuzz and meld itself.


Any hint for what else to look for?

Anybody else can reproduce the issue? maybe on another OS version too?


Riccardo

Re: Python 3.10 fails to build (Ventura 13.2.1, Xcode 14.2)

[Giuseppe ‘ferdy’ Miceli]

ciao,this should have been fixed (at least for me now both python310 and python311 build correct. please self update and upgrade OpenBLAS before give them another shot. you can find the background here:#66242 (python311 @3.11.0 +lto +optimizations fails to build with broken symlink in include path)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/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/Python-3.10.10'Building with support for profile generation:/Library/Developer/CommandLineTools/usr/bin/make build_all_generate_profilemake[2]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/Python-3.10.10'/Library/Developer/CommandLineTools/usr/bin/make build_all CFLAGS_NODIST=" -fprofile-instr-generate" LDFLAGS_NODIST=" -fprofile-instr-generate" LIBS="-lintl -ldl   -framework CoreFoundation"make[3]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/Python-3.10.10'DYLD_FRAMEWORK_PATH=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/Python-3.10.10 CC='/usr/bin/clang' LDSHARED='/usr/bin/clang -bundle -undefined dynamic_lookup -L/opt/local/lib -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch arm64  -flto -Wl,-export_dynamic -g -fprofile-instr-generate' OPT='-DNDEBUG -g -fwrapv -O3 -Wall' 	_TCLTK_INCLUDES='-I/opt/local/include' _TCLTK_LIBS='-L/opt/local/lib -ltk8.6 -ltkstub8.6 -ltcl8.6 -ltclstub8.6'./python.exe -E ./setup.py --no-user-cfg  buildrunning buildrunning build_exterror: [Errno 2] No such file or directory: '/opt/local/include/lapacke_utils.h’In other words, the header file lapacke_utils.h is not found. Is there any workaround for this?Thanks in advance,Artemio
Artemio Gonzalez Lopezartem...@mac.com

Python 3.10 fails to build (Ventura 13.2.1, Xcode 14.2)

[Artemio González López via macports-users]

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-3.10.10'
Building with support for profile generation:
/Library/Developer/CommandLineTools/usr/bin/make build_all_generate_profile
make[2]: Entering directory 
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/Python-3.10.10'
/Library/Developer/CommandLineTools/usr/bin/make build_all CFLAGS_NODIST=" 
-fprofile-instr-generate" LDFLAGS_NODIST=" -fprofile-instr-generate" 
LIBS="-lintl -ldl   -framework CoreFoundation"
make[3]: Entering directory 
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/Python-3.10.10'
DYLD_FRAMEWORK_PATH=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/Python-3.10.10
 CC='/usr/bin/clang' LDSHARED='/usr/bin/clang -bundle -undefined dynamic_lookup 
-L/opt/local/lib -Wl,-headerpad_max_install_names 
-Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch 
arm64  -flto -Wl,-export_dynamic -g -fprofile-instr-generate' OPT='-DNDEBUG -g 
-fwrapv -O3 -Wall'_TCLTK_INCLUDES='-I/opt/local/include' 
_TCLTK_LIBS='-L/opt/local/lib -ltk8.6 -ltkstub8.6 -ltcl8.6 
-ltclstub8.6'./python.exe -E ./setup.py --no-user-cfg  build
running build
running build_ext
error: [Errno 2] No such file or directory: '/opt/local/include/lapacke_utils.h’

In other words, the header file lapacke_utils.h is not found. Is there any 
workaround for this?

Thanks in advance,

Artemio


Artemio Gonzalez Lopez
artem...@mac.com



smime.p7s
Description: S/MIME cryptographic signature

python error after wget install

[supervisitor via macports-users]

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 long time... but the script has to compile 
all parts on local machine... 😎 This python is by configuration of my path 
behind the python (/usr/bin/python = Python 2.7.16) which is included to my 
MacOS (10.13.6) with developer tolls.

Now, when I want to use "xattr", I get the following error message:

Traceback (most recent call last):
  File "/usr/bin/xattr-2.7", line 7, in 
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources

Do someone know how to fix this?

Thanks for support...

Re: Recommendation for installing Python modules: pip or Macports

[Joshua Root]

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?


There are a couple of important points here.

1. Don't use pip (or anything else) to install python modules into the same 
prefix that MacPorts uses. MacPorts won't know about them and you will get file 
conflicts. You can use the --user option to install into your home directory, 
or as has already been mentioned, the more scalable approach is to use 
virtualenv/venv and install whatever you want inside the isolated container.

2. MacPorts doesn't have all the modules on PyPI by a long shot. The modules 
that are provided as ports are usually there because either they depend on some 
non-python-module thing that is in MacPorts (and usually pip won't be able to 
install such dependencies), or something else in MacPorts depends on them.

So it depends what you're doing. You can combine the two to some extent by 
using e.g. virtualenv's --system-site-packages option.

- Josh

Re: Recommendation for installing Python modules: pip or Macports

[Ralph Seichter via macports-users]

* 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 modules using MacPorts ports is that
they are shared. That can cause problems if different Python programs
require different versions of particular modules, and in contrast the
storage space saved by sharing modules is negligible.

My go-to method is using Python virtual environments (via the included
"venv" module, which is leightweight and installs its own "pip"); one
venv for each of my various Python applications:

  https://docs.python.org/3/tutorial/venv.html

Using separate environments isolates Python apps. I have not had to deal
with incompatible shared modules since I started using venvs, and this
is well worth a little extra storage space to me.

-Ralph

Re: Recommendation for installing Python modules: pip or Macports

[Bill Deegan]

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 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 the Python environment is configured.
>
> I demonstrate this in a blog post about OpenADR development using
> OpenLEADR:
> https://techsparx.com/energy-system/openadr/openleadr-docker.html
>
> A simplified Dockerfile would be:
>
> FROM python:3
> VOLUME /setup
> VOLUME /app
> RUN apt-get update && \
> apt-get upgrade -y && \
> apt-get install -y build-essential curl locales
> COPY requirements.txt /setup/requirements.txt
> RUN pip3 install -r /setup/requirements.txt
> python3 /app/app.py
>
>
> Then, to build it
>
> docker build --tag your-name/your-application-name:latest .
>
> Then it can be launched using a Docker Compose file
>
> services:
>   app:
> image: your-name/your-application-name:latest
> volumes:
>   - ./app-source-directory:/app/
> networks:
>   - adrnet
> environment:
>   - PYTHONPATH=... other directories ...:/app
> ports:
>   - 8080:8080
>
>
> And executed with the command:
>
> docker compose up
>
> On your terminal will be logging output.  You can install more services
> like databases in the Docker Compose file and manage them all this way.
> The source code is dynamically mounted into the running container.  That
> means you can edit as you wish.  My blog post demonstrates using Nodemon to
> watch the source directory and to automatically restart Python if files
> change.
>
> + David Herron
>
>
>
> On Tue, Dec 6, 2022 at 6:53 AM Thomas 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?
>>
>> Tom Gederberg
>>
>

Re: Recommendation for installing Python modules: pip or Macports

[David Herron]

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 the
Python environment is configured.

I demonstrate this in a blog post about OpenADR development using OpenLEADR:
https://techsparx.com/energy-system/openadr/openleadr-docker.html

A simplified Dockerfile would be:

FROM python:3
VOLUME /setup
VOLUME /app
RUN apt-get update && \
apt-get upgrade -y && \
apt-get install -y build-essential curl locales
COPY requirements.txt /setup/requirements.txt
RUN pip3 install -r /setup/requirements.txt
python3 /app/app.py


Then, to build it

docker build --tag your-name/your-application-name:latest .

Then it can be launched using a Docker Compose file

services:
  app:
image: your-name/your-application-name:latest
volumes:
  - ./app-source-directory:/app/
networks:
  - adrnet
environment:
  - PYTHONPATH=... other directories ...:/app
ports:
  - 8080:8080


And executed with the command:

docker compose up

On your terminal will be logging output.  You can install more services
like databases in the Docker Compose file and manage them all this way.
The source code is dynamically mounted into the running container.  That
means you can edit as you wish.  My blog post demonstrates using Nodemon to
watch the source directory and to automatically restart Python if files
change.

+ David Herron



On Tue, Dec 6, 2022 at 6:53 AM Thomas 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?
>
> Tom Gederberg
>

Re: Recommendation for installing Python modules: pip or Macports

[Jeremy Lavergne]

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 concept).




On 12/6/22 08:54, Mircea Trandafir wrote:
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 everything else when you do your regular (I suppose you do 
that, right?) “port selfupdate”. Also, when updates are pushed via 
MacPorts they are typically tested and should work…


--
Mircea Trandafir
Senior researcher
Rockwool Foundation Research Unit
Ny Kongensgade 6
DK 1472, Copenhagen
Denmark
Web: http://www.mirceatrandafir.com

On 6 Dec 2022, at 1.53 PM, Thomas 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?

Tom Gederberg

Re: Recommendation for installing Python modules: pip or Macports

[Mircea Trandafir]

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 everything else when you do your 
regular (I suppose you do that, right?) “port selfupdate”. Also, when updates 
are pushed via MacPorts they are typically tested and should work…

--
Mircea Trandafir
Senior researcher
Rockwool Foundation Research Unit
Ny Kongensgade 6
DK 1472, Copenhagen
Denmark
Web: http://www.mirceatrandafir.com

On 6 Dec 2022, at 1.53 PM, Thomas 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?

Tom Gederberg

Recommendation for installing Python modules: pip or Macports

[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.

Is there a recommendation on which way to go?

Tom Gederberg

Re: how to move "Python Launcher" away from /Application folder?

[Ryan Schmidt]

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" carefree 
> over the existing installation... without losing the information about 
> installed apps, e.g. inside "registry.db"?
> The documentation for upgrading a source installation is described as follows 
> in the documentation:
>   MacPorts Guide, Chapter: 2.3:
>   "To upgrade a copy of MacPorts that was installed from source to the 
> newer release of the source code, simply repeat the source install with the 
> newer version of the MacPorts source code."
> But does this also apply if I specify an additional parameter like 
> "--with-applications-dir"?
> 
> Or can I change the path afterwards in configuration file(s), e.g. 
> '/opt/local/etc/macports/macports.conf:applications_dir
> /Applications/MacPorts'?
> (of course after a 'sudo mv /Applications/MacPorts /opt/local/.')

I think either is fine: Either reconfigure with a different 
--with-applications-dir or edit applications_dir in macports.conf. Neither will 
affect your installed ports. Any ports you already have installed that put 
files in /Applications/MacPorts will continue to believe that that's where 
their files are and you should not manually move them. After you change the 
setting, you should rebuild those ports (e.g. sudo port -n upgrade --force 
python310).

The pre-compiled archives we build on our servers are tailored to certain 
default MacPorts settings, including the prefix, applications_dir, 
frameworks_dir, and others. If you change these settings, you will not receive 
any pre-compiled archives and will have to compile every port from source when 
you install it. This is usually undesirable (people usually like receiving an 
archive in seconds instead of waiting minutes or hours for a port to compile) 
so I recommend you do not change these settings.

Re: how to move "Python Launcher" away from /Application folder?

[chilli.names...@gmail.com]

If it helps, it can be hidden from the Finder:
sudo chflags hidden /Applications/MacPorts
(undo with "nohidden")


> On Nov 10, 2022, at 09:56, Chris Jones  wrote:
> 
> 
> May I ask, what exactly is your problem with having the Apps installed by 
> MacPorts under /Applications/MacPorts ? I am not really sure I see what the 
> problem is you are trying to fix.
> 
> Chris
> 
>> On 09/11/2022 11:57 pm, supervisitor via macports-users 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" carefree 
>> over the existing installation... without losing the information about 
>> installed apps, e.g. inside "registry.db"?
>> The documentation for upgrading a source installation is described as 
>> follows in the documentation:
>>MacPorts Guide, Chapter: 2.3:
>>"To upgrade a copy of MacPorts that was installed from source to the 
>> newer release of the source code, simply repeat the source install with the 
>> newer version of the MacPorts source code."
>> But does this also apply if I specify an additional parameter like 
>> "--with-applications-dir"?
>> Or can I change the path afterwards in configuration file(s), e.g. 
>> '/opt/local/etc/macports/macports.conf:applications_dir
>> /Applications/MacPorts'?
>> (of course after a 'sudo mv /Applications/MacPorts /opt/local/.')
>> Does anyone have any experience or reliable information 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
>>> 
>>> -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@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" from terminal.
>>>=> does someone know a solution to move this folder and files inside 
>>> away from there, best would be inside /opt/...
>>> 
>>>Cheers...
>>> 
>>> 

Re: how to move "Python Launcher" away from /Application folder?

[Chris Jones]

May I ask, what exactly is your problem with having the Apps installed 
by MacPorts under /Applications/MacPorts ? I am not really sure I see 
what the problem is you are trying to fix.


Chris

On 09/11/2022 11:57 pm, supervisitor via macports-users 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" carefree over the 
existing installation... without losing the information about installed apps, e.g. inside 
"registry.db"?
The documentation for upgrading a source installation is described as follows 
in the documentation:
MacPorts Guide, Chapter: 2.3:
"To upgrade a copy of MacPorts that was installed from source to the newer 
release of the source code, simply repeat the source install with the newer version of 
the MacPorts source code."
But does this also apply if I specify an additional parameter like 
"--with-applications-dir"?

Or can I change the path afterwards in configuration file(s), e.g. 
'/opt/local/etc/macports/macports.conf:applications_dir
/Applications/MacPorts'?
(of course after a 'sudo mv /Applications/MacPorts /opt/local/.')

Does anyone have any experience or reliable information 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

-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@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" from 
terminal.
=> does someone know a solution to move this folder and files inside away 
from there, best would be inside /opt/...

Cheers...

Re: how to move "Python Launcher" away from /Application folder?

[supervisitor via macports-users]

... 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" carefree over 
the existing installation... without losing the information about installed 
apps, e.g. inside "registry.db"?
The documentation for upgrading a source installation is described as follows 
in the documentation:
MacPorts Guide, Chapter: 2.3:
"To upgrade a copy of MacPorts that was installed from source to the 
newer release of the source code, simply repeat the source install with the 
newer version of the MacPorts source code."
But does this also apply if I specify an additional parameter like 
"--with-applications-dir"?

Or can I change the path afterwards in configuration file(s), e.g. 
'/opt/local/etc/macports/macports.conf:applications_dir
/Applications/MacPorts'?
(of course after a 'sudo mv /Applications/MacPorts /opt/local/.')

Does anyone have any experience or reliable information 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
> 
> -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@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" from terminal.
>=> does someone know a solution to move this folder and files inside away 
> from there, best would be inside /opt/...
> 
>Cheers...
> 
> 

Re: how to move "Python Launcher" away from /Application folder?

[Langer, Stephen A. (Fed) via macports-users]

Build 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@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" from terminal.
=> does someone know a solution to move this folder and files inside away 
from there, best would be inside /opt/...

Cheers...

how to move "Python Launcher" away from /Application folder?

[supervisitor via macports-users]

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, best would be inside /opt/...

Cheers...

Re: macOS 12.3 and /usr/bin/python. Status?

[Gerben Wierda via macports-users]

You might be able to create a different action using mupdf (for which there is 
a port)

Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>)
R&A IT Strategy <https://ea.rna.nl/> (main site)
Book: Chess and the Art of Enterprise Architecture <https://ea.rna.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 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.
> 
> I also have PDFPen Pro which comes with an Apple Script that does much the 
> same thing.  It isn't quite what I want, but it's good enough.
> 
> Mike

Re: macOS 12.3 and /usr/bin/python. Status?

[Ryan Schmidt]

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.

Re: macOS 12.3 and /usr/bin/python. Status?

[Mike Alexander]

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.

I also have PDFPen Pro which comes with an Apple Script that does much the same 
thing.  It isn't quite what I want, but it's good enough.

Mike


smime.p7s
Description: S/MIME digital signature

Re: macOS 12.3 and /usr/bin/python. Status?

[chilli.names...@gmail.com]

> 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 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 12.3.1 and haven't noticed any problems with anything I've 
>> installed from MacPorts.  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.  See 
>> for example https://discussions.apple.com/thread/253764288.  If this matters 
>> to you don't upgrade to 12.3.
>> 
>> Mike
> 
> Or just install python.
> 
> -Al-

Or pdftk

-Chilli

Re: macOS 12.3 and /usr/bin/python. Status?

[Al Varnell via macports-users]

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—the “fix” in response to the update was just to install the 
>> MacPorts version.
> 
> I'm also on 12.3.1 and haven't noticed any problems with anything I've 
> installed from MacPorts.  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.  See for 
> example https://discussions.apple.com/thread/253764288.  If this matters to 
> you don't upgrade to 12.3.
> 
> Mike

Or just install python.

-Al-

smime.p7s
Description: S/MIME cryptographic signature

Re: macOS 12.3 and /usr/bin/python. Status?

[Mike Alexander]

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 12.3.1 and haven't noticed any problems with anything I've 
installed from MacPorts.  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.  See for example 
https://discussions.apple.com/thread/253764288.  If this matters to you 
don't upgrade to 12.3.


Mike

Re: macOS 12.3 and /usr/bin/python. Status?

[Steven Smith]

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 macOS upgrade 
path that is expected to break any of this, so for major upgrades, I always 
just test the upgrade on a non-critical box, then make sure I have a viable 
backup, do the update, and in rare instances make a minor fix for unanticipated 
minor issues, or issue an upstream ticket.

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.

> On Apr 16, 2022, at 12:50, Gerben Wierda via macports-users 
>  wrote:
> 
> 
> The following ports and their dependencies could be installed by me on macOS 
> 12.3:
> 
> The following ports are currently installed:
>   certbot @1.26.0_0+python310 (active)
>   clamav-server @0.101.2_4+sanesecurity+scan_schedule_access (active)
>   dcc @2.3.168_0 (active)
>   dovecot @2.3.17_0+apns+solr (active)
>   dovecot-sieve @0.5.17_0 (active)
>   gtk-doc @1.32_1+python39 (active)
>   inetutils @2.2_0+client (active)
>   iperf3 @3.11_0 (active)
>   logrotate @3.19.0_0 (active)
>   minio @2021-10-06T23-36-31Z_0 (active)
>   minio-mc @2021-10-07T04-19-58Z_0 (active)
>   mono @6.12.0.122_0 (active)
>   nginx 
> @1.21.6_0+davext+debug+fancyindex+flv+http2+mp4+secure_link+ssl+stream 
> (active)
>   nsd @4.3.8_0 (active)
>   postfix @3.7.0_0+dovecot_sasl+pcre+smtputf8+tls (active)
>   putty @0.70_0+gui (active)
>   python3_select @0.0_2 (active)
>   rspamd @3.2_0 (active)
>   rsync @3.2.3_1 (active)
>   sieve-connect @0.90_1+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)
> R&A IT Strategy (main site)
> Book: Chess and the Art of Enterprise Architecture
> Book: Mastering ArchiMate
> 
>> On 16 Apr 2022, at 18:02, Clemens Lang  wrote:
>> 
>> 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 instructions).
>>> 
>>> I haven’t seen any traffic on this issue. Does that mean hardly anyone
>>> is on 12.3? Is anyone running on 12.3? Am I simply one of the first
>>> who will be taking the plunge?
>> 
>> I'm on 12.3 for a while now, on an M1 system. I simply haven't noticed
>> any problems, and I'm using a bit of Python here and there. Seems to me
>> that most things have moved to Python 3 and it's just not a big problem
>> anymore.
>> 
>> -- 
>> Clemens
> 

Re: macOS 12.3 and /usr/bin/python. Status?

[Gregory Seidman]

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.
> > 
> > TIL. Is that something I could work around by disabling SIP?
> 
> On macOS 10.x, yes. On macOS 11 and later, my understanding is that the 
> system volume is cryptographically sealed and there is no way for you to 
> modify it without breaking that seal, which presumably has undesirable 
> consequences.
> 
> https://eclecticlight.co/2020/11/30/is-big-surs-system-volume-sealed/

I wonder if fuse-overlayfs <https://github.com/containers/fuse-overlayfs>
on top of osxfuse <https://ports.macports.org/port/osxfuse/> would allow
apparent modification of /usr/bin without touching the underlying sealed
FS. I see that Homebrew has a formula for it
<https://formulae.brew.sh/formula/fuse-overlayfs>, though there doesn't
seem to be a port for it in MacPorts.

--Gregory

Re: macOS 12.3 and /usr/bin/python. Status?

[Gerben Wierda via macports-users]

> 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 that something I could work around by disabling SIP?
> 
> On macOS 10.x, yes. On macOS 11 and later, my understanding is that the 
> system volume is cryptographically sealed and there is no way for you to 
> modify it without breaking that seal, which presumably has undesirable 
> consequences.
> 
> https://eclecticlight.co/2020/11/30/is-big-surs-system-volume-sealed/

Yes, I can support that conclusion. Creating that link (or changing anything 
that is in that cryptographically signed part of the file system) is no longer 
a viable option on macOS Big Sur and up.

Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>)
R&A IT Strategy <https://ea.rna.nl/> (main site)
Book: Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/>
Book: Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>

Re: macOS 12.3 and /usr/bin/python. Status?

[Gerben Wierda via macports-users]

> On 17 Apr 2022, at 16:13, Ryan Schmidt  wrote:

>> Doing the (normally unnecessary) migrations run at least will catch the 
>> dependencies during build.
> 
> Only for ports you actually build, not for ports for which you receive a 
> binary archive.

Agreed. But then, the install from my view still succeeds, even if I get a 12.2 
build installed on a 12.3 system. What then is left is that potential runtime 
dependency. Still, doing it with force compile would be better. I am going to 
do that as well.

>> Numbers do not give a definitive answer to major or minor updates. E.g. 
>> tomcat 8.2 or 8.3 are minor updates, but tomcat 8.5 was/is in fact a major 
>> update at the company I work, because it was fundamentally changes. The 
>> numbers are just a clue, not reality. See also Lifecycle Management – Let 
>> the Sunshine in
> 
> In the case of macOS version numbers as they relate to a need to follow the 
> migration instructions, they do. The migration instructions are for helping 
> you upgrade from one major macOS version to another. They are not needed for 
> minor OS version updates.

Agreed. I was misusing 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&A IT Strategy <https://ea.rna.nl/> (main site)
Book: Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/>
Book: Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>

Re: macOS 12.3 and /usr/bin/python. Status?

[Ryan Schmidt]

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, my understanding is that the system 
volume is cryptographically sealed and there is no way for you to modify it 
without breaking that seal, which presumably has undesirable consequences.

https://eclecticlight.co/2020/11/30/is-big-surs-system-volume-sealed/

Re: macOS 12.3 and /usr/bin/python. Status?

[Christian Calderon]

> 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.

Sent from my iPhone

> On Apr 17, 2022, at 7:16 AM, Ryan Schmidt  wrote:
> 
> 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 would not be able to make a symbolic link at /usr/bin/python because 
> /usr/bin is a protected directory.
> 
> If you do encounter ports broken by the removal of /usr/bin/python, please do 
> not keep that discovery to yourself and try to work around it just for 
> yourself. Please report the problem to us in the issue tracker or send a pull 
> request on GitHub to fix it.

Re: macOS 12.3 and /usr/bin/python. Status?

[Ryan Schmidt]

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 would not be able to make a symbolic link at /usr/bin/python because 
/usr/bin is a protected directory.

If you do encounter ports broken by the removal of /usr/bin/python, please do 
not keep that discovery to yourself and try to work around it just for 
yourself. Please report the problem to us in the issue tracker or send a pull 
request on GitHub to fix it.

Re: macOS 12.3 and /usr/bin/python. Status?

[Christian Calderon]

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 macports-users 
>  wrote:
> 
> 
>>> 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).
>> 
>> If you are upgrading from macOS 11.x or earlier tto macOS 12.3, you should 
>> of course follow the migration instructions. If you are upgrading from an 
>> earlier version of macOS 12, there would be no benefit to performing the 
>> migration steps.
> 
> Normally, this is true. But macOS 12.3 is not backwards compatible with macOS 
> 12.2 in a major way, because of the missing /usr/bin/python. So, if MacPorts 
> detects a dependency which is still up to date according to MacPorts, it will 
> not rebuild that port. Then later when that dependency gets an update it 
> will. If at that moment you find out the dependency still requires 
> /usr/bin/python during build, you’re stuck. You might even find this out 
> halfway a dependency tree build, so that the dependencies of the dependency 
> have already been rebuilt and installed and then halfway that rebuild you 
> fail. It is a risk for the availability/continuity of your landscape and that 
> is especially important if we’re talking about service you offer to the 
> environment (e.g. mail server).
> 
> Of course, the same is true in case of (undeclared, e.g. not tested in the 
> configure script) dependencies of python during run, but there is no easy way 
> to test for this and the chance of this being the case is smaller (though 
> solving it is nastier, I suspect)
> 
> 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)? Doing the (normally unnecessary) migrations run at 
> least will catch the dependencies during build.
> 
> Numbers do not give a definitive answer to major or minor updates. E.g. 
> tomcat 8.2 or 8.3 are minor updates, but tomcat 8.5 was/is in fact a major 
> update at the company I work, because it was fundamentally changes. The 
> numbers are just a clue, not reality. See also Lifecycle Management – Let the 
> Sunshine in
> 
> Gerben Wierda (LinkedIn)
> R&A IT Strategy (main site)
> Book: Chess and the Art of Enterprise Architecture
> Book: Mastering ArchiMate
> 

Re: macOS 12.3 and /usr/bin/python. Status?

[Ryan Schmidt]

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 referenced in a software 
package, so I can't answer that. If you wanted to test it, you would make sure 
that no python is selected (sudo port select python none) and then rebuild the 
ports from source (e.g. sudo port -ns upgrade --force logrotate). If they fail 
to build saying python was needed and not found, you've found a problem we 
could fix. If they install, that still doesn't guarantee that they're not 
affected. They may have detected at build time that python didn't exist and 
disabled whatever python-using functionality they contained. (You could check 
the log to see if they mention anything about not finding python, though 
absence of such a message isn't a guarantee of success either.) Or they may 
have blindly installed files that reference python, assuming that it would 
exist, and if you try to use these files at runtime they will fail. You could 
try grepping the contents of the installed files of each of the ports for 
"/usr/bin/python" or "/usr/bin/env python" or just "python" (though that last 
one is likely to give you lots of irrelevant hits)..


> Doing the (normally unnecessary) migrations run at least will catch the 
> dependencies during build.

Only for ports you actually build, not for ports for which you receive a binary 
archive.


> Numbers do not give a definitive answer to major or minor updates. E.g. 
> tomcat 8.2 or 8.3 are minor updates, but tomcat 8.5 was/is in fact a major 
> update at the company I work, because it was fundamentally changes. The 
> numbers are just a clue, not reality. See also Lifecycle Management – Let the 
> Sunshine in

In the case of macOS version numbers as they relate to a need to follow the 
migration instructions, they do. The migration instructions are for helping you 
upgrade from one major macOS version to another. They are not needed for minor 
OS version updates.

Re: macOS 12.3 and /usr/bin/python. Status?

[Gerben Wierda via macports-users]

> 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).
> 
> If you are upgrading from macOS 11.x or earlier tto macOS 12.3, you should of 
> course follow the migration instructions. If you are upgrading from an 
> earlier version of macOS 12, there would be no benefit to performing the 
> migration steps.

Normally, this is true. But macOS 12.3 is not backwards compatible with macOS 
12.2 in a major way, because of the missing /usr/bin/python. So, if MacPorts 
detects a dependency which is still up to date according to MacPorts, it will 
not rebuild that port. Then later when that dependency gets an update it will. 
If at that moment you find out the dependency still requires /usr/bin/python 
during build, you’re stuck. You might even find this out halfway a dependency 
tree build, so that the dependencies of the dependency have already been 
rebuilt and installed and then halfway that rebuild you fail. It is a risk for 
the availability/continuity of your landscape and that is especially important 
if we’re talking about service you offer to the environment (e.g. mail server).

Of course, the same is true in case of (undeclared, e.g. not tested in the 
configure script) dependencies of python during run, but there is no easy way 
to test for this and the chance of this being the case is smaller (though 
solving it is nastier, I suspect)

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)? Doing the (normally unnecessary) migrations run at least will 
catch the dependencies during build.

Numbers do not give a definitive answer to major or minor updates. E.g. tomcat 
8.2 or 8.3 are minor updates, but tomcat 8.5 was/is in fact a major update at 
the company I work, because it was fundamentally changes. The numbers are just 
a clue, not reality. See also Lifecycle Management – Let the Sunshine in 
<https://ea.rna.nl/2019/08/14/lifecycle-management-let-the-sunshine-in/>

Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>)
R&A IT Strategy <https://ea.rna.nl/> (main site)
Book: Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/>
Book: Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>

Re: macOS 12.3 and /usr/bin/python. Status?

[Ryan Schmidt]

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 the problem are those that just happen to 
use python 2 somewhere, for example in their build process or in a script that 
gets installed.

I haven't upgraded the Monterey buildbot machines to macOS 12.3 or later 
because of this problem, and don't plan to unless there is some dire need to. 
As a result, any ports that do require python 2 in their build will continue to 
build fine on the buildbot, and if they are distributable, the archives will be 
distributed, so even if you are on macOS 12.3 or later, you can still receive 
binaries built by our server. So the fact that ports installed fine for you is 
no indication that the problem has been fixed everywhere, unless you built all 
ports from source, in which case it means the problem has been fixed (or never 
existed) in those ports that you built (but MacPorts contains tens of thousands 
of ports and I doubt all affected ports have been fixed).

Re: macOS 12.3 and /usr/bin/python. Status?

[Ryan Schmidt]

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 macOS 11.x or earlier tto macOS 12.3, you should of 
course follow the migration instructions. If you are upgrading from an earlier 
version of macOS 12, there would be no benefit to performing the migration 
steps.

Re: macOS 12.3 and /usr/bin/python. Status?

[Gerben Wierda via macports-users]

The following ports and their dependencies could be installed by me on macOS 
12.3:

The following ports are currently installed:
  certbot @1.26.0_0+python310 (active)
  clamav-server @0.101.2_4+sanesecurity+scan_schedule_access (active)
  dcc @2.3.168_0 (active)
  dovecot @2.3.17_0+apns+solr (active)
  dovecot-sieve @0.5.17_0 (active)
  gtk-doc @1.32_1+python39 (active)
  inetutils @2.2_0+client (active)
  iperf3 @3.11_0 (active)
  logrotate @3.19.0_0 (active)
  minio @2021-10-06T23-36-31Z_0 (active)
  minio-mc @2021-10-07T04-19-58Z_0 (active)
  mono @6.12.0.122_0 (active)
  nginx @1.21.6_0+davext+debug+fancyindex+flv+http2+mp4+secure_link+ssl+stream 
(active)
  nsd @4.3.8_0 (active)
  postfix @3.7.0_0+dovecot_sasl+pcre+smtputf8+tls (active)
  putty @0.70_0+gui (active)
  python3_select @0.0_2 (active)
  rspamd @3.2_0 (active)
  rsync @3.2.3_1 (active)
  sieve-connect @0.90_1+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 Art of Enterprise Architecture <https://ea.rna.nl/the-book/>
Book: Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>

> On 16 Apr 2022, at 18:02, Clemens Lang  wrote:
> 
> 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 instructions).
>> 
>> I haven’t seen any traffic on this issue. Does that mean hardly anyone
>> is on 12.3? Is anyone running on 12.3? Am I simply one of the first
>> who will be taking the plunge?
> 
> I'm on 12.3 for a while now, on an M1 system. I simply haven't noticed
> any problems, and I'm using a bit of Python here and there. Seems to me
> that most things have moved to Python 3 and it's just not a big problem
> anymore.
> 
> -- 
> Clemens

Re: macOS 12.3 and /usr/bin/python. Status?

[Clemens Lang]

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 instructions).
> 
> I haven’t seen any traffic on this issue. Does that mean hardly anyone
> is on 12.3? Is anyone running on 12.3? Am I simply one of the first
> who will be taking the plunge?

I'm on 12.3 for a while now, on an M1 system. I simply haven't noticed
any problems, and I'm using a bit of Python here and there. Seems to me
that most things have moved to Python 3 and it's just not a big problem
anymore.

-- 
Clemens

Re: macOS 12.3 and /usr/bin/python. Status?

[Ralph Seichter via macports-users]

* 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

Re: macOS 12.3 and /usr/bin/python. Status?

[Ralph Seichter via macports-users]

* 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 macOS 12.3.1 and MacPorts 2.7.2 on an
Intel-based MacBook Pro without any problems.

-Ralph

Re: macOS 12.3 and /usr/bin/python. Status?

[Franco Vaccari via macports-users]

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 installations went 
smoothly. 

Last time I’ve asked 12.3 was still considered “risky”, so don’t make your 
choice just based on my own experience…

Ciao

Franco


> On 16 Apr 2022, at 15:16, 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 instructions).
> 
> I haven’t seen any traffic on this issue. Does that mean hardly anyone is on 
> 12.3? Is anyone running on 12.3? Am I simply one of the first who will be 
> taking the plunge?
> 
> Gerben Wierda (LinkedIn)
> R&A IT Strategy (main site)
> Book: Chess and the Art of Enterprise Architecture
> Book: Mastering ArchiMate
> 

macOS 12.3 and /usr/bin/python. Status?

[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 haven’t seen any traffic on this issue. Does that mean hardly anyone is on 
12.3? Is anyone running on 12.3? Am I simply one of the first who will be 
taking the plunge?

Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>)
R&A IT Strategy <https://ea.rna.nl/> (main site)
Book: Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/>
Book: Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>

Re: Older versions of python

[Ryan Schmidt]

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, MacPorts will notify 
you of this and prevent you from uninstalling them.

As of January 2022, we would like ports to use python310 if possible. Not all 
ports have been updated to do so yet. If you find some that have not yet 
updated, you can file tickets or pull requests.

Older versions of python

[dan d.]

-- ent- XR
Can one delete older python versions then the current python10?  Do some ports 
anticipate an older version?

Thanks

Re: Python

[Ryan Schmidt]

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 unchanged.

https://lists.macports.org/pipermail/macports-users/2022-February/050792.html

Re: Python

[Steven Smith]

Looks like you get to play “World of install_name_tool” before playing World of 
Tanks.

Figure out where the binaries are.
Read `man otool` and `man install_name_tool`
Look at `otool -L `
Back up your app before messing around with its binaries
Use install_name_tool to replace the dynamic links 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 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/*/Wargaming.net Game 
>> Center.app/Contents/MacOS/Wargaming.net Game Center
>> Reason: tried: 
>> '/System/Library/Frameworks/Python.framework/Versions/2.7/Python' (no such 
>> file)
>> (terminated at launch; ignore backtrace)



smime.p7s
Description: S/MIME cryptographic signature

Re: Python

[Tom]

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/*/Wargaming.net Game 
> Center.app/Contents/MacOS/Wargaming.net Game Center
> Reason: tried: 
> '/System/Library/Frameworks/Python.framework/Versions/2.7/Python' (no such 
> file)
> (terminated at launch; ignore backtrace)

Re: Python

[James Secan]

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 17, 2022, at 9:57 PM, Ryan Schmidt  wrote:
> 
> Sure. But Tom specifically asked for a Python replacement for macOS 12.3. 
> What happened in macOS 12.3 is that Apple removed /usr/bin/python which was 
> Python 2.7 so I assumed that's what Tom was asking about. If Tom wants to use 
> Python 3, I assume macOS still provides a version of that in 
> /usr/bin/python3. Or he can install any of the python3x ports as you 
> mentioned.

Re: Python

[VACCARI FRANCO]

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 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_select is a dependency of python310 so you don't need to request it 
> separately. Same goes for all other _select ports.
> 
> 
>> [come back in 20 minutes]
> 
> It should only take that long if you need to compile it and you have a 
> relatively slow computer. Most users wouldn't need to compile it and would 
> instead receive a binary from our server within seconds.
> 
> 
>> port select python python310
>> 
>> If you need an older version, there are ports for them. Unlike Ryan, I urge 
>> you to NOT install a 2.x version unless you are absolutely sure that you 
>> need such an antique, unsupported, encoding-impaired tool.
> 
> Sure. But Tom specifically asked for a Python replacement for macOS 12.3. 
> What happened in macOS 12.3 is that Apple removed /usr/bin/python which was 
> Python 2.7 so I assumed that's what Tom was asking about. If Tom wants to use 
> Python 3, I assume macOS still provides a version of that in 
> /usr/bin/python3. Or he can install any of the python3x ports as you 
> mentioned.

Re: Python

[Ryan Schmidt]

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_select is a dependency of python310 so you don't need to request it 
separately. Same goes for all other _select ports.


> [come back in 20 minutes]

It should only take that long if you need to compile it and you have a 
relatively slow computer. Most users wouldn't need to compile it and would 
instead receive a binary from our server within seconds.


> port select python python310
> 
> If you need an older version, there are ports for them. Unlike Ryan, I urge 
> you to NOT install a 2.x version unless you are absolutely sure that you need 
> such an antique, unsupported, encoding-impaired tool.

Sure. But Tom specifically asked for a Python replacement for macOS 12.3. What 
happened in macOS 12.3 is that Apple removed /usr/bin/python which was Python 
2.7 so I assumed that's what Tom was asking about. If Tom wants to use Python 
3, I assume macOS still provides a version of that in /usr/bin/python3. Or he 
can install any of the python3x ports as you mentioned.

Re: Python

[Bill Cole]

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, there are ports for them. Unlike Ryan, I 
urge you to NOT install a 2.x version unless you are absolutely sure 
that you need such an antique, unsupported, encoding-impaired tool.




--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire

Re: Python

[Ryan Schmidt]

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 port install python27

If you want "python" to refer to MacPorts python 27, you can select it:

sudo port select python python27

This will create an /opt/local/bin/python symlink for you.

Python

[Tom]

Hello people, how do I install a python replacement for macOS 12.3?

Re: Installation location for python code, tools, etc.

[Forrest Aldrich]

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 that option.


Thanks!

Re: Installation location for python code, tools, etc.

[Joshua Root]

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:

/opt/local/Library/Frameworks/Python.framework/Versions/3.9/bin/


Python is typically built as a framework on macOS, so that's where the 
modules go. See 
<https://github.com/python/cpython/blob/main/Mac/README.rst>.


% python3.9
Python 3.9.9 (main, Nov 16 2021, 17:57:38)
[Clang 13.0.0 (clang-1300.0.29.3)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.prefix
'/opt/local/Library/Frameworks/Python.framework/Versions/3.9'

Pip has a number of options controlling where things are installed: 
<https://pip.pypa.io/en/stable/cli/pip_install/#options>


I strongly recommend not installing modules into the MacPorts prefix 
with pip (or manually), because modules installed in other ways will 
conflict with modules installed by MacPorts. Install in a venv, or use 
pip's --user option or some completely separate prefix.


- Josh

Re: Installation location for python code, tools, etc.

[Bill Cole]

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 ie: "python setup.py install" the 
tool(s) end up in this directory instead of /opt/local/bin|sbin etc:


/opt/local/Library/Frameworks/Python.framework/Versions/3.9/bin/


This is how MacPorts supports simultaneous installs of different Python 
versions. You may note that there are versioned python symlinks in 
/opt/local/bin pointing to that path and possibly an additional bunch of 
symlinks making 'python' and 'python3' go there. If you install the 
python_select and python3_select ports, they will create links in 
/opt/local/bin if you run 'port select python' or 'port select python3' 
that ultimately resolve to that versioned path.


When you install a Python module outside of MacPorts, its installer is 
almost certain to not know to create those links.



I'm suspecting an environment variable.


I believe that *in theory* you should get binaries into 
/opt/local/(s)bin/ if you set the PYTHONHOME environment variable to 
'/opt/local/Library/Frameworks/Python.framework/Versions/3.9:/opt/local' 
when running setup.py or pip.



--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire

Installation location for python code, tools, etc.

[Forrest Aldrich]

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:


/opt/local/Library/Frameworks/Python.framework/Versions/3.9/bin/

I'm suspecting an environment variable.


Thanks.

Re: python ports depend on openssl not in index

[Chris Jones]

> 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: /opt/local/bin/port: port selfupdate failed: Error synchronizing 
> MacPorts sources: command execution failed
> 
> [To be clear, I consider my problem to be resolved, thanks.]

Yes, the above is clear, and I guess the reason behind this thread is you did 
not pay enough attention to it in the first case ;)

Chris
> 
> ‐‐‐ Original Message ‐‐‐
> 
>> On Friday, December 10th, 2021 at 2:21 PM, Chris Jones 
>>  wrote:
>> 
>> 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 seaque...@protonmail.com wrote:
>>> 
>>> 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/com.apple.xbs/Sources/rsync/rsync-54.120.1/rsync/clientserver.c(106)
>>>  [receiver=2.6.9]
>>> 
>>> Command failed: /usr/bin/rsync -rtzvl --delete-after 
>>> rsync://rsync.macports.org/macports/release/tarballs/base.tar 
>>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs
>>> 
>>> Exit code: 10
>>> 
>>> Error: Error synchronizing MacPorts sources: command execution failed
>>> 
>>> ‐‐‐ Original Message ‐‐‐
>>> 
 On Friday, December 10th, 2021 at 10:24 AM, Christopher Jones 
 jon...@hep.phy.cam.ac.uk wrote:
 
 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 seaque...@protonmail.com wrote:
> 
> 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 Friday, December 10th, 2021 at 3:35 AM, Ryan Schmidt 
>> ryandes...@macports.org wrote:
> 
>> 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 went without issue until Step 3e: `sudo 
 ./restore_ports.tcl myports.txt`
 
 Executing that command resulted in the error I presented initially:
 
 ---> Computing dependencies for python38
 
 Error: Dependency 'openssl3' not found.
 
 ---> Computing dependencies for python39
 
 Error: Dependency 'openssl3' not found.
 
 Is that to be expected on a fresh install (before performing a sync)? 
 I acknowledge that this outcome may result from the use of git versus 
 rsync in keeping MacPorts up to date. I am behind a firewall, so i 
 must use git to sync rather than use rsync.
 
 https://trac.macports.org/wiki/howto/SyncingWithGit
 
 If i substitute the command `sudo port -v sync` for the command `sudo 
 port selfupdate` - as usual - I can now install openssl without error, 
 and all dependencies are found after re-executing: `sudo 
 ./restore_ports.tcl myports.txt`
>>> 
>>> We need to see why you are not finding the openssl3 port, as that has 
>>> been available for some time.
>>> 
>>> Please run
>>> 
>>> sudo port -d sync
>>> 
>>> And post what you get back to the list
>> 
>> They already said that after running "sudo port sync", everything is 
>> working.
>> 
>> "sudo port selfupdate" should selfupdate (update MacPorts base) and sync 
>> (update ports tree). If updating base failed for some reason, then it 
>> might not update the ports tree either. You mentioned being behind a 
>> firewall that prevents you from syncing with rsync. selfupdate has no 
>> option but to use rsync, so that would be a likely explanation for why 
>> selfupdate doesn't work for you, and w

Re: python ports depend on openssl not in index

[SeaQuench via macports-users]

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 
MacPorts sources: command execution failed

[To be clear, I consider my problem to be resolved, thanks.]

‐‐‐ Original Message ‐‐‐

On Friday, December 10th, 2021 at 2:21 PM, Chris Jones 
 wrote:

> 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 seaque...@protonmail.com wrote:
> >
> > 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/com.apple.xbs/Sources/rsync/rsync-54.120.1/rsync/clientserver.c(106)
> >  [receiver=2.6.9]
> >
> > Command failed: /usr/bin/rsync -rtzvl --delete-after 
> > rsync://rsync.macports.org/macports/release/tarballs/base.tar 
> > /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs
> >
> > Exit code: 10
> >
> > Error: Error synchronizing MacPorts sources: command execution failed
> >
> > ‐‐‐ Original Message ‐‐‐
> >
> > > On Friday, December 10th, 2021 at 10:24 AM, Christopher Jones 
> > > jon...@hep.phy.cam.ac.uk wrote:
> > >
> > > 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 seaque...@protonmail.com wrote:
> > > >
> > > > 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 Friday, December 10th, 2021 at 3:35 AM, Ryan Schmidt 
> > > > > ryandes...@macports.org wrote:
> > > >
> > > > > 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 went without issue until Step 3e: `sudo 
> > > > > > > ./restore_ports.tcl myports.txt`
> > > > > > >
> > > > > > > Executing that command resulted in the error I presented 
> > > > > > > initially:
> > > > > > >
> > > > > > > ---> Computing dependencies for python38
> > > > > > >
> > > > > > > Error: Dependency 'openssl3' not found.
> > > > > > >
> > > > > > > ---> Computing dependencies for python39
> > > > > > >
> > > > > > > Error: Dependency 'openssl3' not found.
> > > > > > >
> > > > > > > Is that to be expected on a fresh install (before performing a 
> > > > > > > sync)? I acknowledge that this outcome may result from the use of 
> > > > > > > git versus rsync in keeping MacPorts up to date. I am behind a 
> > > > > > > firewall, so i must use git to sync rather than use rsync.
> > > > > > >
> > > > > > > https://trac.macports.org/wiki/howto/SyncingWithGit
> > > > > > >
> > > > > > > If i substitute the command `sudo port -v sync` for the command 
> > > > > > > `sudo port selfupdate` - as usual - I can now install openssl 
> > > > > > > without error, and all dependencies are found after re-executing: 
> > > > > > > `sudo ./restore_ports.tcl myports.txt`
> > > > > >
> > > > > > We need to see why you are not finding the openssl3 port, as that 
> > > > > > has been available for some time.
> > > > > >
> > > > > > Please run
> > > > > >
> > > > > > sudo port -d sync
> > > > > >
> > > > > > And post what you get back to the list
> > > > >
> > > > > They already said that after running "sudo port sync", everything is 
> > > > > working.
> > > > >
> > > > > "sudo port selfupdate" should selfupdate (update MacPorts base) and 
> > > > > sync (update ports tree). If updating base failed for some reason, 
> > > > > then it might not update the ports tree either. You mentioned being 
> > > > > behind a firewall that prevents you from syncing with rsync. 
> > > > > selfupdate has no option but to use rsync, so that would be a likely 
> > > > > explanation for why selfupdate doesn't work for you, and wh

Re: python ports depend on openssl not in index

[Chris Jones]

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 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/com.apple.xbs/Sources/rsync/rsync-54.120.1/rsync/clientserver.c(106)
>  [receiver=2.6.9]
> Command failed: /usr/bin/rsync -rtzvl --delete-after 
> rsync://rsync.macports.org/macports/release/tarballs/base.tar 
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs
> Exit code: 10
> Error: Error synchronizing MacPorts sources: command execution failed
> 
> ‐‐‐ Original Message ‐‐‐
> 
>> On Friday, December 10th, 2021 at 10:24 AM, Christopher Jones 
>>  wrote:
>> 
>> 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 seaque...@protonmail.com wrote:
>>> 
>>> 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 Friday, December 10th, 2021 at 3:35 AM, Ryan Schmidt 
 ryandes...@macports.org wrote:
>>> 
 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 went without issue until Step 3e: `sudo 
>> ./restore_ports.tcl myports.txt`
>> 
>> Executing that command resulted in the error I presented initially:
>> 
>> ---> Computing dependencies for python38
>> 
>> Error: Dependency 'openssl3' not found.
>> 
>> ---> Computing dependencies for python39
>> 
>> Error: Dependency 'openssl3' not found.
>> 
>> Is that to be expected on a fresh install (before performing a sync)? I 
>> acknowledge that this outcome may result from the use of git versus 
>> rsync in keeping MacPorts up to date. I am behind a firewall, so i must 
>> use git to sync rather than use rsync.
>> 
>> https://trac.macports.org/wiki/howto/SyncingWithGit
>> 
>> If i substitute the command `sudo port -v sync` for the command `sudo 
>> port selfupdate` - as usual - I can now install openssl without error, 
>> and all dependencies are found after re-executing: `sudo 
>> ./restore_ports.tcl myports.txt`
> 
> We need to see why you are not finding the openssl3 port, as that has 
> been available for some time.
> 
> Please run
> 
> sudo port -d sync
> 
> And post what you get back to the list
 
 They already said that after running "sudo port sync", everything is 
 working.
 
 "sudo port selfupdate" should selfupdate (update MacPorts base) and sync 
 (update ports tree). If updating base failed for some reason, then it 
 might not update the ports tree either. You mentioned being behind a 
 firewall that prevents you from syncing with rsync. selfupdate has no 
 option but to use rsync, so that would be a likely explanation for why 
 selfupdate doesn't work for you, and why you should not use selfupdate and 
 should instead (i) update MacPorts base manually when a new version is 
 available, using an installer from our web site and (ii) sync to update 
 ports.

Re: python ports depend on openssl not in index

[SeaQuench via macports-users]

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/com.apple.xbs/Sources/rsync/rsync-54.120.1/rsync/clientserver.c(106)
 [receiver=2.6.9]
Command failed: /usr/bin/rsync -rtzvl --delete-after 
rsync://rsync.macports.org/macports/release/tarballs/base.tar 
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs
Exit code: 10
Error: Error synchronizing MacPorts sources: command execution failed

‐‐‐ Original Message ‐‐‐

On Friday, December 10th, 2021 at 10:24 AM, Christopher Jones 
 wrote:

> 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 seaque...@protonmail.com wrote:
> >
> > 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 Friday, December 10th, 2021 at 3:35 AM, Ryan Schmidt 
> > ryandes...@macports.org wrote:
> >
> > > 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 went without issue until Step 3e: `sudo 
> > > > > ./restore_ports.tcl myports.txt`
> > > > >
> > > > > Executing that command resulted in the error I presented initially:
> > > > >
> > > > > ---> Computing dependencies for python38
> > > > >
> > > > > Error: Dependency 'openssl3' not found.
> > > > >
> > > > > ---> Computing dependencies for python39
> > > > >
> > > > > Error: Dependency 'openssl3' not found.
> > > > >
> > > > > Is that to be expected on a fresh install (before performing a sync)? 
> > > > > I acknowledge that this outcome may result from the use of git versus 
> > > > > rsync in keeping MacPorts up to date. I am behind a firewall, so i 
> > > > > must use git to sync rather than use rsync.
> > > > >
> > > > > https://trac.macports.org/wiki/howto/SyncingWithGit
> > > > >
> > > > > If i substitute the command `sudo port -v sync` for the command `sudo 
> > > > > port selfupdate` - as usual - I can now install openssl without 
> > > > > error, and all dependencies are found after re-executing: `sudo 
> > > > > ./restore_ports.tcl myports.txt`
> > > >
> > > > We need to see why you are not finding the openssl3 port, as that has 
> > > > been available for some time.
> > > >
> > > > Please run
> > > >
> > > > sudo port -d sync
> > > >
> > > > And post what you get back to the list
> > >
> > > They already said that after running "sudo port sync", everything is 
> > > working.
> > >
> > > "sudo port selfupdate" should selfupdate (update MacPorts base) and sync 
> > > (update ports tree). If updating base failed for some reason, then it 
> > > might not update the ports tree either. You mentioned being behind a 
> > > firewall that prevents you from syncing with rsync. selfupdate has no 
> > > option but to use rsync, so that would be a likely explanation for why 
> > > selfupdate doesn't work for you, and why you should not use selfupdate 
> > > and should instead (i) update MacPorts base manually when a new version 
> > > is available, using an installer from our web site and (ii) sync to 
> > > update ports.

Re: python ports depend on openssl not in index

[Christopher Jones]

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  wrote:
>
> 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 Friday, December 10th, 2021 at 3:35 AM, Ryan Schmidt 
>  wrote:
>
>> 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 went without issue until Step 3e: `sudo 
 ./restore_ports.tcl myports.txt`

 Executing that command resulted in the error I presented initially:

 ---> Computing dependencies for python38

 Error: Dependency 'openssl3' not found.

 ---> Computing dependencies for python39

 Error: Dependency 'openssl3' not found.

 Is that to be expected on a fresh install (before performing a sync)? I 
 acknowledge that this outcome may result from the use of git versus rsync 
 in keeping MacPorts up to date. I am behind a firewall, so i must use git 
 to sync rather than use rsync.

 https://trac.macports.org/wiki/howto/SyncingWithGit

 If i substitute the command `sudo port -v sync` for the command `sudo port 
 selfupdate` - as usual - I can now install openssl without error, and all 
 dependencies are found after re-executing: `sudo ./restore_ports.tcl 
 myports.txt`
>>>
>>> We need to see why you are not finding the openssl3 port, as that has been 
>>> available for some time.
>>>
>>> Please run
>>>
>>> sudo port -d sync
>>>
>>> And post what you get back to the list
>>
>> They already said that after running "sudo port sync", everything is working.
>>
>> "sudo port selfupdate" should selfupdate (update MacPorts base) and sync 
>> (update ports tree). If updating base failed for some reason, then it might 
>> not update the ports tree either. You mentioned being behind a firewall that 
>> prevents you from syncing with rsync. selfupdate has no option but to use 
>> rsync, so that would be a likely explanation for why selfupdate doesn't work 
>> for you, and why you should not use selfupdate and should instead (i) update 
>> MacPorts base manually when a new version is available, using an installer 
>> from our web site and (ii) sync to update ports.



smime.p7s
Description: S/MIME cryptographic signature

Re: python ports depend on openssl not in index

[SeaQuench via macports-users]

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 Friday, December 10th, 2021 at 3:35 AM, Ryan Schmidt 
 wrote:

> 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 went without issue until Step 3e: `sudo 
> > > ./restore_ports.tcl myports.txt`
> > >
> > > Executing that command resulted in the error I presented initially:
> > >
> > > ---> Computing dependencies for python38
> > >
> > > Error: Dependency 'openssl3' not found.
> > >
> > > ---> Computing dependencies for python39
> > >
> > > Error: Dependency 'openssl3' not found.
> > >
> > > Is that to be expected on a fresh install (before performing a sync)? I 
> > > acknowledge that this outcome may result from the use of git versus rsync 
> > > in keeping MacPorts up to date. I am behind a firewall, so i must use git 
> > > to sync rather than use rsync.
> > >
> > > https://trac.macports.org/wiki/howto/SyncingWithGit
> > >
> > > If i substitute the command `sudo port -v sync` for the command `sudo 
> > > port selfupdate` - as usual - I can now install openssl without error, 
> > > and all dependencies are found after re-executing: `sudo 
> > > ./restore_ports.tcl myports.txt`
> >
> > We need to see why you are not finding the openssl3 port, as that has been 
> > available for some time.
> >
> > Please run
> >
> > sudo port -d sync
> >
> > And post what you get back to the list
>
> They already said that after running "sudo port sync", everything is working.
>
> "sudo port selfupdate" should selfupdate (update MacPorts base) and sync 
> (update ports tree). If updating base failed for some reason, then it might 
> not update the ports tree either. You mentioned being behind a firewall that 
> prevents you from syncing with rsync. selfupdate has no option but to use 
> rsync, so that would be a likely explanation for why selfupdate doesn't work 
> for you, and why you should not use selfupdate and should instead (i) update 
> MacPorts base manually when a new version is available, using an installer 
> from our web site and (ii) sync to update ports.

Re: python ports depend on openssl not in index

[Ryan Schmidt]

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 went without issue until Step 3e: `sudo 
>> ./restore_ports.tcl myports.txt`
>> Executing that command resulted in the error I presented initially:
>> --->  Computing dependencies for python38
>> Error: Dependency 'openssl3' not found.
>> --->  Computing dependencies for python39
>> Error: Dependency 'openssl3' not found.
>> 
>> Is that to be expected on a fresh install (before performing a sync)? I 
>> acknowledge that this outcome may result from the use of git versus rsync in 
>> keeping MacPorts up to date. I am behind a firewall, so i must use git to 
>> sync rather than use rsync.
>> https://trac.macports.org/wiki/howto/SyncingWithGit
>> If i substitute the command `sudo port -v sync` for the command `sudo port 
>> selfupdate` - as usual - I can now install openssl without error, and all 
>> dependencies are found after re-executing: `sudo ./restore_ports.tcl 
>> myports.txt`
> 
> We need to see why you are not finding the openssl3 port, as that has been 
> available for some time.
> 
> Please run
> 
> sudo port -d sync
> 
> And post what you get back to the list



They already said that after running "sudo port sync", everything is working.

"sudo port selfupdate" should selfupdate (update MacPorts base) and sync 
(update ports tree). If updating base failed for some reason, then it might not 
update the ports tree either. You mentioned being behind a firewall that 
prevents you from syncing with rsync. selfupdate has no option but to use 
rsync, so that would be a likely explanation for why selfupdate doesn't work 
for you, and why you should not use selfupdate and should instead (i) update 
MacPorts base manually when a new version is available, using an installer from 
our web site and (ii) sync to update ports.

Re: python ports depend on openssl not in index

[Chris Jones]

Hi,

Please always remember to reply to the list.

We need to see why you are not finding the openssl3 port, as that has been 
available for some time.

Please run

sudo port -d sync

And post what you get back to the list

Chris

> 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 went without issue until Step 3e: `sudo 
> ./restore_ports.tcl myports.txt`
> Executing that command resulted in the error I presented initially:
> --->  Computing dependencies for python38
> Error: Dependency 'openssl3' not found.
> --->  Computing dependencies for python39
> Error: Dependency 'openssl3' not found.
> 
> Is that to be expected on a fresh install (before performing a sync)? I 
> acknowledge that this outcome may result from the use of git versus rsync in 
> keeping MacPorts up to date. I am behind a firewall, so i must use git to 
> sync rather than use rsync.
> https://trac.macports.org/wiki/howto/SyncingWithGit
> If i substitute the command `sudo port -v sync` for the command `sudo port 
> selfupdate` - as usual - I can now install openssl without error, and all 
> dependencies are found after re-executing: `sudo ./restore_ports.tcl 
> myports.txt`
> 
> Any additional advice welcome. Thanks for the tip on migration, Chris!
> 
> Sent with ProtonMail Secure Email.
> 
> ‐‐‐ Original Message ‐‐‐
>> On Thursday, December 9th, 2021 at 2:47 PM, Chris Jones 
>>  wrote:
>> 
>> 
>> 
>> Did you follow the migration guide when moving to a new major os version ?
>> 
>> https://trac.macports.org/wiki/Migration
>> 
>> If not, follow it now, to wipe out your ports and reinstall them correctly 
>> for the new os.
>> 
>> If you did, your ports tree seems to be very out of date. Then try,
>> 
>> > sudo port 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 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 am not in a novel situation. Could someone advise me as to how to 
>>> proceed? I am running MacPorts 2.6.2 on MacOS 10.15.7 with XCode 12.4 
>>> installed.
>>> $ sudo port install python39 
>>> 
>>> 
>>> 
>>> 
>>> Warning: No port openssl3 found in the index. 
>>> ---> Computing dependencies for openssl
>>> Error: Dependency 'openssl3' not found. 
>>> Error: Unable to execute port: upgrade openssl failed 
>>> 
>>> 
>>> 
>>> 
>>> $ sudo port install openssl 
>>> 
>>> 
>>> 
>>> 
>>> ---> Computing dependencies for openssl
>>> Error: Dependency 'openssl3' not found. 
>>> Error: Follow https://guide.macports.org/#project.tickets to report a bug. 
>>> Error: Processing of port openssl failed
>>> 
>>> 
>>> $ sudo port -n upgrade --force python38
>>> --->  Computing dependencies for python38
>>> --->  Fetching archive for python38
>>> --->  Attempting to fetch 
>>> python38-3.8.12_4+optimizations.darwin_19.x86_64.tbz2 from 
>>> https://packages.macports.org/python38
>>> --->  Attempting to fetch 
>>> python38-3.8.12_4+optimizations.darwin_19.x86_64.tbz2.rmd160 from 
>>> https://packages.macports.org/python38
>>> --->  Installing python38 @3.8.12_4+optimizations
>>> --->  Cleaning python38
>>> --->  Computing dependencies for python38
>>> --->  Deactivating python38 @3.8.11_0
>>> --->  Cleaning python38
>>> --->  Activating python38 @3.8.12_4+optimizations
>>> --->  Cleaning python38
>>> --->  Updating database of binaries
>>> --->  Scanning binaries for linking errors
>>> --->  Found 18 broken files, matching files to ports 
>>> --->  Found 4 broken ports, determining rebuild order
>>> You can always run 'port rev-upgrade' again to fix errors.
>>> The following ports will be rebuilt:
>>>  python38 @3.8.12+optimizations
>>>  python39 @3.9.6
>>>  glib2 @2.58.3+x11
>>>  gobject-introspection @1.60.2
>>> Continue? [Y/n]: y
>>> Warning: No port openssl3 found in the index.
>>> --->  Computing dependencies for openssl
>>> Error: Dependency 'openssl3' not found.
>>> Error: rev-upgrade failed: Error rebuilding python38
>>> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
>>> 
>>> 
> 
> 

Re: python ports depend on openssl not in index

[Joshua Root]

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 report a bug, I presume I am not in a novel 
situation. Could someone advise me as to how to proceed? I am running MacPorts 
2.6.2 on MacOS 10.15.7 with XCode 12.4 installed.
The primary problem here is that you are running MacPorts 2.6.2 
(released in 2019). The current ports are not going to work with an old 
version of base. You need to update to 2.7.1, and the other problems 
will likely be resolved by that.


- Josh

Re: python ports depend on openssl not in index

[Chris Jones]

Did you follow the migration guide when moving to a new major os version ?

https://trac.macports.org/wiki/Migration

If not, follow it now, to wipe out your ports and reinstall them correctly for 
the new os.

If you did, your ports tree seems to be very out of date. Then try,

> sudo port 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 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 am 
> not in a novel situation. Could someone advise me as to how to proceed? I am 
> running MacPorts 2.6.2 on MacOS 10.15.7 with XCode 12.4 installed.
> 
> $ sudo port install python39 
> Warning: No port openssl3 found in the index. 
> ---> Computing dependencies for openssl
> Error: Dependency 'openssl3' not found. 
> Error: Unable to execute port: upgrade openssl failed 
> $ sudo port install openssl 
> ---> Computing dependencies for openssl
> Error: Dependency 'openssl3' not found. 
> Error: Follow https://guide.macports.org/#project.tickets to report a bug. 
> Error: Processing of port openssl failed
> $ sudo port -n upgrade --force python38
> --->  Computing dependencies for python38
> --->  Fetching archive for python38
> --->  Attempting to fetch 
> python38-3.8.12_4+optimizations.darwin_19.x86_64.tbz2 from 
> https://packages.macports.org/python38
> --->  Attempting to fetch 
> python38-3.8.12_4+optimizations.darwin_19.x86_64.tbz2.rmd160 from 
> https://packages.macports.org/python38
> --->  Installing python38 @3.8.12_4+optimizations
> --->  Cleaning python38
> --->  Computing dependencies for python38
> --->  Deactivating python38 @3.8.11_0
> --->  Cleaning python38
> --->  Activating python38 @3.8.12_4+optimizations
> --->  Cleaning python38
> --->  Updating database of binaries
> --->  Scanning binaries for linking errors
> --->  Found 18 broken files, matching files to ports 
> --->  Found 4 broken ports, determining rebuild order
> You can always run 'port rev-upgrade' again to fix errors.
> The following ports will be rebuilt:
>  python38 @3.8.12+optimizations
>  python39 @3.9.6
>  glib2 @2.58.3+x11
>  gobject-introspection @1.60.2
> Continue? [Y/n]: y
> Warning: No port openssl3 found in the index.
> --->  Computing dependencies for openssl
> Error: Dependency 'openssl3' not found.
> Error: rev-upgrade failed: Error rebuilding python38
> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
> 
> 

python ports depend on openssl not in index

[SeaQuench via macports-users]

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 am not in a novel 
situation. Could someone advise me as to how to proceed? I am running MacPorts 
2.6.2 on MacOS 10.15.7 with XCode 12.4 installed.
$ sudo port install python39

> Warning: No port openssl3 found in the index.
> ---> Computing dependencies for openssl
> Error: Dependency 'openssl3' not found.
> Error: Unable to execute port: upgrade openssl failed

$ sudo port install openssl

> ---> Computing dependencies for openssl
> Error: Dependency 'openssl3' not found.
> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
> Error: Processing of port openssl failed

$ sudo port -n upgrade --force python38

> --->Computing dependencies for python38
> --->Fetching archive for python38
> --->Attempting to fetch python38-3.8.12_4+optimizations.darwin_19.x86_64.tbz2 
> from https://packages.macports.org/python38
> --->Attempting to fetch 
> python38-3.8.12_4+optimizations.darwin_19.x86_64.tbz2.rmd160 from 
> https://packages.macports.org/python38
> --->Installing python38 @3.8.12_4+optimizations
> --->Cleaning python38
> --->Computing dependencies for python38
> --->Deactivating python38 @3.8.11_0
> --->Cleaning python38
> --->Activating python38 @3.8.12_4+optimizations
> --->Cleaning python38
> --->Updating database of binaries
> --->Scanning binaries for linking errors
> --->Found 18 broken files, matching files to ports
> --->Found 4 broken ports, determining rebuild order
> You can always run 'port rev-upgrade' again to fix errors.
> The following ports will be rebuilt:
> python38 @3.8.12+optimizations
> python39 @3.9.6
> glib2 @2.58.3+x11
> gobject-introspection @1.60.2
> Continue? [Y/n]: y
> Warning: No port openssl3 found in the index.
> --->Computing dependencies for openssl
> Error: Dependency 'openssl3' not found.
> Error: rev-upgrade failed: Error rebuilding python38
> Error: Follow https://guide.macports.org/#project.tickets to report a bug.

Re: how to add a python package to python39

[VACCARI FRANCO]

Marius,

thanks for looking into it! I took the updated Portfile and placed in my local 
tree, but got this error about @rpath/libgfortran.5.dylib missing

I have gcc10 and gcc11 installed, and compiled many fortran programs with 
gfortran 11 and they run properly. In /opt/local/lib/gcc11 I see this symbolic 
link

libgfortran.5.dylib -> /opt/local/lib/libgcc/libgfortran.5.dylib

but 

/opt/local/lib/libgcc/libgfortran.5.dylib

is not there, and I see instead

/opt/local/lib/libgcc/libgfortran.5.dylib.mp_1632812346 

so I’m not sure if something is wrong with my gcc installation. Maybe I should 
better delete and reinstall Macports, just to be sure. This is a test machine, 
so no risk of breaking anything (but I’m probably going off topic now…)

Anyway, I copy below the last part of py39-matplotlib-basemap/main.log

I've really appreciated your help!

Ciao

Franco


…
…
:info:build ImportError: 
dlopen(/opt/local/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/numpy/core/_multiarray_umath.cpython-39-darwin.so,
 2): Library not loaded: @rpath/libgfortran.5.dylib
:info:build   Referenced from: /opt/local/lib/libopenblas-r1.dylib
:info:build   Reason: image not found
:info:build During handling of the above exception, another exception occurred:
:info:build Traceback (most recent call last):
:info:build   File 
"/opt/local/var/macports/build/_Volumes_xHD_DMG_Users_miniadmin_Ports_python_py-matplotlib-basemap/py39-matplotlib-basemap/work/matplotlib-basemap-3076ec9/setup.py",
 line 19, in 
:info:build import numpy
:info:build   File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/numpy/__init__.py",
 line 150, in 
:info:build from . import core
:info:build   File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/numpy/core/__init__.py",
 line 48, in 
:info:build raise ImportError(msg)
:info:build ImportError: 
:info:build IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
:info:build Importing the numpy C-extensions failed. This error can happen for
:info:build many reasons, often due to issues with your setup or how NumPy was
:info:build installed.
:info:build We have compiled some common reasons and troubleshooting tips at:
:info:build https://numpy.org/devdocs/user/troubleshooting-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 are the versions you expect.
:info:build Please carefully study the documentation linked above for further 
help.
:info:build Original error was: 
dlopen(/opt/local/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/numpy/core/_multiarray_umath.cpython-39-darwin.so,
 2): Library not loaded: @rpath/libgfortran.5.dylib
:info:build   Referenced from: /opt/local/lib/libopenblas-r1.dylib
:info:build   Reason: image not found
:info:build Command failed:  cd 
"/opt/local/var/macports/build/_Volumes_xHD_DMG_Users_miniadmin_Ports_python_py-matplotlib-basemap/py39-matplotlib-basemap/work/basemap-1.2.2"
 && /opt/local/Library/Frameworks/Python.framework/Versions/3.9/bin/python3.9 
setup.py --no-user-cfg build -j8 
:info:build Exit code: 1
:error:build Failed to build py39-matplotlib-basemap: command execution failed
:debug:build Error code: CHILDSTATUS 6668 1
:debug:build Backtrace: command execution failed
:debug:build while executing
:debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring"
:debug:build invoked from within
:debug:build "command_exec -callback portprogress::target_progress_callback 
build"
:debug:build (procedure "portbuild::build_main" line 8)
:debug:build invoked from within
:debug:build "$procedure $targetname"
:error:build See 
/opt/local/var/macports/logs/_Volumes_xHD_DMG_Users_miniadmin_Ports_python_py-matplotlib-basemap/py39-matplotlib-basemap/main.log
 for details.



> On 14 Oct 2021, at 23:27, Marius Schamschula  wrote:
> 
> Franco,
> 
> I just found a workaround for this issue, and committed an updated Portfile
> 
> https://github.com/macports/macports-ports/commit/0b17692041f0cac2a1ae588e0a22161a39e72106
> 
> Marius
> --
> Marius Schamschula
> 
> 
> 
> 
>> On Oct 14, 2021, at 8:11 AM, VACCARI FRANCO  wrote:
>> 
>> Ok, will look at the guide for portindex use
>> 
>> Thanks again
>> 
>> Franco
>> 
>>> On 14 Oct 2021, at 15:07, Marius Schamschula  wrote:
>>> 
>>> Franco,
>>> 
>>> You have to run
>>> 
>>> portindex
>>> 
>>> to add the support to the index.
>>

Re: how to add a python package to python39

[Marius Schamschula]

Franco,

You have to run

portindex

to add the support to the index.

Marius
--
Marius Schamschula




> On Oct 14, 2021, at 7:58 AM, VACCARI FRANCO  wrote:
> 
> 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 install py39-matplotlib-basemap (Error: Port 
> py39-matplotlib-basemap not found)
> 
> What else should I do to finally be able to see the build fail?
> 
> Franco 
> 
>> On 14 Oct 2021, at 14:47, Marius Schamschula  wrote:
>> 
>> Franco,
>> 
>> Yes, you would need to add 39.
>> 
>> As py-matplotlib-basemap has no maintainer, this has apparently been missed.
>> 
>> However, when trying to build py39-matplotlib-basemap you will see several 
>> errors:
>> 
>> error: no member named 'tp_print' in 'struct _typeobject’
>> 
>> This is no longer 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 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 version for python38
>>> 
>>> port file py38-matplotlib-basemap 
>>> 
>>> points me to 
>>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python/py-matplotlib-basemap/Portfile
>>> 
>>> and inside that I see this entry
>>> 
>>> python.versions 27 35 36 37 38
>>> 
>>> How to add compatibility with python39 to it? It looks like it’s not just a 
>>> matter of adding 39 there... How could I create the py39matplotlib-basemap 
>>> package?
>>> 
>>> Sorry for what is very likely a dumb question...
>>> 
>>> Franco
>> 
> 

Re: how to add a python package to python39

[VACCARI FRANCO]

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 install py39-matplotlib-basemap (Error: Port py39-matplotlib-basemap 
not found)

What else should I do to finally be able to see the build fail?

Franco 

> On 14 Oct 2021, at 14:47, Marius Schamschula  wrote:
> 
> Franco,
> 
> Yes, you would need to add 39.
> 
> As py-matplotlib-basemap has no maintainer, this has apparently been missed.
> 
> However, when trying to build py39-matplotlib-basemap you will see several 
> errors:
> 
> error: no member named 'tp_print' in 'struct _typeobject’
> 
> This is no longer 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 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 version for python38
>> 
>> port file py38-matplotlib-basemap 
>> 
>> points me to 
>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python/py-matplotlib-basemap/Portfile
>> 
>> and inside that I see this entry
>> 
>> python.versions 27 35 36 37 38
>> 
>> How to add compatibility with python39 to it? It looks like it’s not just a 
>> matter of adding 39 there... How could I create the py39matplotlib-basemap 
>> package?
>> 
>> Sorry for what is very likely a dumb question...
>> 
>> Franco
> 

Re: how to add a python package to python39

[Marius Schamschula]

Franco,

Yes, you would need to add 39.

As py-matplotlib-basemap has no maintainer, this has apparently been missed.

However, when trying to build py39-matplotlib-basemap you will see several 
errors:

error: no member named 'tp_print' in 'struct _typeobject’

This is no longer 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 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 version for python38
> 
> port file py38-matplotlib-basemap 
> 
> points me to 
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python/py-matplotlib-basemap/Portfile
> 
> and inside that I see this entry
> 
> python.versions 27 35 36 37 38
> 
> How to add compatibility with python39 to it? It looks like it’s not just a 
> matter of adding 39 there... How could I create the py39matplotlib-basemap 
> package?
> 
> Sorry for what is very likely a dumb question...
> 
> Franco

how to add a python package to python39

[VACCARI FRANCO]

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 version for python38

port file py38-matplotlib-basemap 

points me to 
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python/py-matplotlib-basemap/Portfile

and inside that I see this entry

python.versions 27 35 36 37 38

How to add compatibility with python39 to it? It looks like it’s not just a 
matter of adding 39 there... How could I create the py39matplotlib-basemap 
package?

Sorry for what is very likely a dumb question...

Franco