undefined | Better HN

0 pointsteilo5y ago0 comments

Yes, I understand that we can and should always install our own, and I have for years either with Homebrew or Conda. (Actually most of my development is python on Linux via Vagrant).

But on the M1 Mini, out of the box, you can open Terminal, and python3 launches the Python 3.8 REPL. Python 2.7 also launches out of the box. So, can you explain what you mean by "direct access" not being allowed? I'm not following your distinction.

It's damn convenient having python always available when managing a fleet of Macs with JAMF.

0 comments

uranusjr5y ago

I can imagine many existing tools still rely on the commands being directly accessible on PATH, and Apple may be reluctant to break them outright even that’s the goal. They are declared deprecated so people would refrain from using them for new things, and move old things away from them. That’s basically what deprecation means in software, as I understand it. Those commands wouldn’t be called deprecated if Apple breaks them outright.

teiloOP5y ago

Right, but in that case I would not expect them to upgrade Python to 3.8.

uranusjr5y ago

It’s quite likely Apple still wants Python.framework to be available (which is not deprecated) and it’s easier to upgrade the whole thing.

my1235y ago

Python 3.8 for example got moved from the base OS install to Xcode's command line toolset. For developers, that doesn't change much.

teiloOP5y ago

It's in the base OS actually.

my1235y ago

Nope. Python2 is inbox, but Python3 redirects to the Xcode/developer tools copy.

  % sw_vers
  ProductName: macOS
  ProductVersion: 11.1
  BuildVersion: 20C5048k
  % ls /Library/Python/                  
  2.7
  % ls /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/
  Headers  Python3  Resources Versions
  % ls /System/Library/Frameworks/Python.framework/
  Python  Resources Versions

1 more reply

j / k navigate · click thread line to collapse

0 pointsteilo5y ago0 comments

Yes, I understand that we can and should always install our own, and I have for years either with Homebrew or Conda. (Actually most of my development is python on Linux via Vagrant).

It's damn convenient having python always available when managing a fleet of Macs with JAMF.

0 comments

uranusjr5y ago

teiloOP5y ago

Right, but in that case I would not expect them to upgrade Python to 3.8.

uranusjr5y ago

It’s quite likely Apple still wants Python.framework to be available (which is not deprecated) and it’s easier to upgrade the whole thing.

my1235y ago

Python 3.8 for example got moved from the base OS install to Xcode's command line toolset. For developers, that doesn't change much.

teiloOP5y ago

It's in the base OS actually.

my1235y ago

Nope. Python2 is inbox, but Python3 redirects to the Xcode/developer tools copy.

  % sw_vers
  ProductName: macOS
  ProductVersion: 11.1
  BuildVersion: 20C5048k
  % ls /Library/Python/                  
  2.7
  % ls /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/
  Headers  Python3  Resources Versions
  % ls /System/Library/Frameworks/Python.framework/
  Python  Resources Versions

1 more reply

j / k navigate · click thread line to collapse