python VS warehouse

Here it says Foundation is part of pyobjc which may be included in certain versions of python3 such as this https://github.com/macadmins/python - Looking at it now, it seems to set itself apart from the developer tools installation of python3 based on it's installation location. So my guess is that it isn't a module installed with CLT's python3.

Installing python (the MacAdmins Foundation distribution of Python) would be as simple as uploading the installomator script to JSS, adding it as a policy payload with "macadminspython" as a parameter.

Sounds like the scripts you have may be written in Python 2, which as others have stated, was pulled in 12.3. You can try running one with a Python 2 or 3 interpreter to see. You could technically deploy your own Python 2 to people and update the shebangs on the scripts to reflect the updated Python binary location. But Python 2 has been deprecated since January 2020 so it's probably best to just update the scripts. I dealt with this myself and am by no means a programmer. We have a critical script that maps printers for people that I had to update. I used something called '2to3' which is I believe an official Python program that does its best to convert Python 2 code to Python 3 in an automated fashion. It did 99% of the work for me. My script was still failing, but it was just a variable that was being concatenated as a byte instead of a string. Once that was fixed it ran fine. And then we started deploying https://github.com/macadmins/python - as others have mentioned. And then just updated the shebang to point to where that Python gets installed as per their instructions.

Removed. I deployed macadmins Python3 https://github.com/macadmins/python and changed the shebang in scripts we use.

Check out https://github.com/macadmins/python

python3 -m pip install \ --trusted-host test.pypi.org --trusted-host test-files.pythonhosted.org \ --index-url https://test.pypi.org/simple/ \ --extra-index-url https://pypi.org/simple/ \ piper_whistle==$(python3 -m src.piper_whistle.version)

In my experience so far, I can use a vast amount of the Python Standard Library to build Wasm-powered serverless applications. The caveat I currently understand is that Python’s implementation of TCP and UDP sockets, as well as Python libraries that use threads, processes, and signal handling behind the scenes, will not compile to Wasm. It is worth noting that a similar caveat exists with libraries that I find on The Python Package Index (PyPI) site. While these caveats might limit what can be compiled to Wasm, there are still a ton of extremely powerful libraries to leverage.

We believe that poetry is currently the best tool for this purpose, besides of being the most popular one at the moment. This is why we will use poetry to manage the dependencies of our project throughout this series of posts. Poetry allows you to declare the libraries your project depends on, and it will manage (install/update) them for you. Poetry also allows you to package your project into a distributable format and publish it to a repository, such as PyPI. We strongly recommend you to learn more about this tool by reading the official documentation.

From there, I needed to learn a bit about PyPi or Python Package Index, which is the home for all the wonderful packages that you know if you have ever run the handy pip install command. PyPi has a pretty quick and easy onboarding, which requires a secured account be created and, for the purposes of submitting packages from CLI, an API token be generated. This can be done in your PyPi profile. Once logg just navigate to https://pypi.org/manage/account/ and scroll down to the API tokens section. Click “Add Token” and follow the few steps to generate an API token which is your access point to uploading packages. With all this in place, I was able to use twine to handle the package upload. First I needed to install twine, again as simple as pip install twine. In order for twine to access my API token during the package upload process, it needed to read it from .pypirc file that contains the token info. For some that file may exist already, for me I was required to create it. Working in windows I simply used a text editor to create it in my home user directory ($HOME/.pypirc). The file contents had a TOML like format looked like this:

I have published the package to Python Package Index, commonly called PyPi, and in this post, I'll be sharing the steps I had to follow in the process.

Register at PyPI.org

According to the stats on the original link, there are over 25,000 identified secret ids/keys/tokens in the data. And it looks like that's just identifiable secrets, e.g. "Google API Keys" that I'm guessing are identifiable because they have a specific pattern, and may be missing other secrets that use less recognizable patterns.

I mean, sure, compared to the 478,876 Projects claimed on https://pypi.org/, that's a pretty small minority. On the other hand, I'd guess a many Python packages don't use these particular services, or even need to connect to a remote service at all, so the area for this class of mistake should be even smaller.

And mistakes do happen, but that's a pretty big thing to miss if you are knowingly publishing your code with the expectation other people will be reading it.

PyPi package

Does pypi.org display the Union of all keywords, the keywords of the most recent release, the keywords of the first release or some other weird combination like the intersection?

https://peps.python.org/pep-0458/

Here's the in-progress roadmap: https://github.com/pypi/warehouse/issues/10672

If there's particular issues you believe you could pick off to help achieve the goal, much appreciated!