build
requests
Our great sponsors
build | requests | |
---|---|---|
7 | 87 | |
659 | 51,322 | |
4.1% | 0.4% | |
9.2 | 8.4 | |
8 days ago | 8 days ago | |
Python | Python | |
MIT License | 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.
build
- How can I download a software for my user automatically?
-
Underappreciated Challenges with Python Packaging
If it's pure Python, the only packaging file you need is `pyproject.toml`. You can fill that file with packaging metadata per PEP 518 and PEP 621, including using modern build tooling like flit[1] for the build backend and build[2] for the frontend.
With that, you entire package build (for all distribution types) should be reducible to `python -m build`. Here's an example of a full project doing everything with just `pyproject.toml`[3] (FD: my project).
[1]: https://github.com/pypa/flit
[2]: https://github.com/pypa/build
[3]: https://github.com/pypa/pip-audit
-
"Even with --dry-run pip will execute arbitrary code found in the package's setup.py. In fact, merely asking pip to download a package can execute arbitrary code"
RE the dislike of a "third-party tool", what do you mean by this? All the major tools for packaging in Python are under the PyPA, e.g. - twine - build - hatch
-
'Python: Please stop screwing over Linux distros'
building wheels/sdists to upload or install: build
-
An Interactive Cheat Sheet That Just Gives You The Answer
python3 setup.py sdist bdist_wheel - no need for an sdist when building wheels, also I'd recommend using pypa/build instead.
-
How to Structure a Python AWS Serverless Project
The first step is to turn the internal package into a wheel (a *.whl file). We can use the build tool for this purpose. After installing build with pip we can run it as follows:
-
The future of Python build systems and Gentoo
Shouldn't https://github.com/pypa/build help? I don't think it has enough features yet but I was under the impression that was the distro solution.
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?
gh-action-pypi-publish - The blessed :octocat: GitHub Action, for publishing your :package: distribution files to PyPI: https://github.com/marketplace/actions/pypi-publish
urllib3 - urllib3 is a user-friendly HTTP client library for Python
installer - A low-level library for installing from a Python wheel distribution.
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.
setuptools - Official project repository for the Setuptools build system
grequests - Requests + Gevent = <3
pyunifiprotect - Unofficial UniFi Protect Python API and CLI
AIOHTTP - Asynchronous HTTP client/server framework for asyncio and Python
awesome-pyproject - An Awesome List of projects using the pyproject.toml Python configuration file.
treq - Python requests like API built on top of Twisted's HTTP client.
pipx - Install and Run Python Applications in Isolated Environments
Uplink - A Declarative HTTP Client for Python