requests
mypy
Our great sponsors
requests | mypy | |
---|---|---|
87 | 112 | |
51,359 | 17,541 | |
0.5% | 1.6% | |
8.4 | 9.7 | |
7 days ago | 5 days ago | |
Python | Python | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
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.
mypy
- The GIL can now be disabled in Python's main branch
-
Polars – A bird's eye view of Polars
It's got type annotations and mypy has a discussion about it here as well: https://github.com/python/mypy/issues/1282
- Static Typing for Python
-
Python 3.13 Gets a JIT
There is already an AOT compiler for Python: Nuitka[0]. But I don't think it's much faster.
And then there is mypyc[1] which uses mypy's static type annotations but is only slightly faster.
And various other compilers like Numba and Cython that work with specialized dialects of Python to achieve better results, but then it's not quite Python anymore.
[0] https://nuitka.net/
[1] https://github.com/python/mypy/tree/master/mypyc
- Introducing Flask-Muck: How To Build a Comprehensive Flask REST API in 5 Minutes
-
WeveAllBeenThere
In Python there is MyPy that can help with this. https://www.mypy-lang.org/
-
It's Time for a Change: Datetime.utcnow() Is Now Deprecated
It's funny you should say this.
Reading this article prompted me to future-proof a program I maintain for fun that deals with time; it had one use of utcnow, which I fixed.
And then I tripped over a runtime type problem in an unrelated area of the code, despite the code being green under "mypy --strict". (and "100% coverage" from tests, except this particular exception only occured in a "# pragma: no-cover" codepath so it wasn't actually covered)
It turns out that because of some core decisions about how datetime objects work, `datetime.date.today() < datetime.datetime.now()` type-checks but gives a TypeError at runtime. Oops. (cause discussed at length in https://github.com/python/mypy/issues/9015 but without action for 3 years)
One solution is apparently to use `datetype` for type annotations (while continuing to use `datetime` objects at runtime): https://github.com/glyph/DateType
-
What's New in Python 3.12
PEP 695 is great. I've been using mypy every day at work in last couple years or so with very strict parameters (no any type etc) and I have experience writing real life programs with Rust, Agda, and some Haskell before, so I'm familiar with strict type systems. I'm sure many will disagree with me but these are my very honest opinions as a professional who uses Python types every day:
* Some types are better than no types. I love Python types, and I consider them required. Even if they're not type-checked they're better than no types. If they're type-checked it's even better. If things are typed properly (no any etc) and type-checked that's even better. And so on...
* Having said this, Python's type system as checked by mypy feels like a toy type system. It's very easy to fool it, and you need to be careful so that type-checking actually fails badly formed programs.
* The biggest issue I face are exceptions. Community discussed this many times [1] [2] and the overall consensus is to not check exceptions. I personally disagree as if you have a Python program that's meticulously typed and type-checked exceptions still cause bad states and since Python code uses exceptions liberally, it's pretty easy to accidentally go to a bad state. E.g. in the linked github issue JukkaL (developer) claims checking things like "KeyError" will create too many false positives, I strongly disagree. If a function can realistically raise a "KeyError" the program should be properly written to accept this at some level otherwise something that returns type T but 0.01% of the time raises "KeyError" should actually be typed "Raises[T, KeyError]".
* PEP 695 will help because typing things particularly is very helpful. Often you want to pass bunch of Ts around but since this is impractical some devs resort to passing "dict[str, Any]"s around and thus things type-check but you still get "KeyError" left and right. It's better to have "SomeStructure[T]" types with "T" as your custom data type (whether dataclass, or pydantic, or traditional class) so that type system has more opportunities to reject bad programs.
* Overall, I'm personally very optimistic about the future of types in Python!
[1] https://github.com/python/mypy/issues/1773
-
Mypy 1.6 Released
# is fixed: https://github.com/python/mypy/issues/12987.
-
Ask HN: Why are all of the best back end web frameworks dynamically typed?
You probably already know but you can add type hints and then check for consistency with https://github.com/python/mypy in python.
Modern Python with things like https://learnpython.com/blog/python-match-case-statement/ + mypy + Ruff for linting https://github.com/astral-sh/ruff can get pretty good results.
I found typed dataclasses (https://docs.python.org/3/library/dataclasses.html) in python using mypy to give me really high confidence when building data representations.
What are some alternatives?
urllib3 - urllib3 is a user-friendly HTTP client library for Python
pyright - Static Type Checker for Python
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.
ruff - An extremely fast Python linter and code formatter, written in Rust.
grequests - Requests + Gevent = <3
pyre-check - Performant type-checking for python.
AIOHTTP - Asynchronous HTTP client/server framework for asyncio and Python
black - The uncompromising Python code formatter
treq - Python requests like API built on top of Twisted's HTTP client.
pytype - A static type analyzer for Python code
Uplink - A Declarative HTTP Client for Python
pydantic - Data validation using Python type hints