Our great sponsors
warehouse | requests | |
---|---|---|
274 | 87 | |
3,468 | 51,359 | |
0.8% | 0.5% | |
9.7 | 8.4 | |
1 day ago | 3 days ago | |
Python | Python | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
warehouse
-
Smooth Packaging: Flowing from Source to PyPi with GitLab Pipelines
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)
-
Pickling Python in the Cloud via WebAssembly
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.
-
Introducing Flama for Robust Machine Learning APIs
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.
-
PyPI Packaging
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:
-
Releasing my Python Project
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.
-
Publishing my open source project to PyPI!
Register at PyPI.org
-
Show HN: I mirrored all the code from PyPI to GitHub
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.
-
Pezzo v0.5 - Dashboards, Caching, Python Client, and More!
PyPi package
-
Modifying keywords in python 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?
-
PyPI Requires 2FA for New User Registrations
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!
requests
-
Revived the promise made six years ago for Requests 3
For many years now, Requests has been frozen. Being left in a vegetative state and not evolving, this blocked millions of developers from using more advanced features.
-
Ask HN: Is Python async/await some kind of joke?
- Ubiquitous “requests” library used in most docs examples, no async support https://github.com/psf/requests
-
10 Github repositories to achieve Python mastery
Explore here.
-
urllib3 v2.0.0 is now generally available!
It's Lukasa (his name is Cory, there's Łukasz in PSF though, but that's a different person). Looking at him, he made significant contributions to the requests repo: https://github.com/psf/requests/graphs/contributors
- I built a chatbot that lets you talk to any Github repository
-
I Could Rewrite Curl
> I'd love to see the look on some of these people's faces when they find out that tool/software/whatever they use is actually using libcurl under the hood.
Python dependencies (does not include curl)
https://devguide.python.org/getting-started/setup-building/i...
The "requests" module in Python (does not use curl)
https://github.com/psf/requests
-
Development environment for the Python requests package
This part can be found in the README of the GitHub repository.
-
Trying to install autoscan from https://github.com/NiNiyas/autoscan and stuck with no idea what the problem is.
Looking around for similar errors I found this issue where they recommended trying to use a newer version of the urllib3 library.
-
Pain when going back to other languages
but I appreciate the fact that there is an issue about it, it's acknowledged and .. unfixable, it would now break too many things https://github.com/psf/requests/issues/2002
-
How do you decide when to keep a project in a single python file vs break it up into multiple files?
The requests package has been the golden standard for package structure for as long as I can remember.
What are some alternatives?
devpi
urllib3 - urllib3 is a user-friendly HTTP client library for Python
bandersnatch
httplib2 - Small, fast HTTP client library for Python. Features persistent connections, cache, and Google App Engine support. Originally written by Joe Gregorio, now supported by community.
localshop - local pypi server (custom packages and auto-mirroring of pypi)
grequests - Requests + Gevent = <3
Poe the Poet - A task runner that works well with poetry.
AIOHTTP - Asynchronous HTTP client/server framework for asyncio and Python
scribd-downloader
treq - Python requests like API built on top of Twisted's HTTP client.
Python Packages Project Generator - 🚀 Your next Python package needs a bleeding-edge project structure.
Uplink - A Declarative HTTP Client for Python