typing
unboxed
Our great sponsors
typing | unboxed | |
---|---|---|
38 | 3 | |
1,544 | 36 | |
1.6% | - | |
8.8 | 0.0 | |
10 days ago | over 1 year ago | |
Python | Haskell | |
GNU General Public License v3.0 or later | 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.
typing
- Writing Python like it’s Rust
- Library for single dispatch on Generic subscript
-
Thoughts on nested / inner functions in Python for better encapsulation and clarity?
Iterable[str] is unfortunately evil as it matches str which is often unintended. (see: https://github.com/python/typing/issues/256) One would need both NOT-type and AND-type in order to properly handle these.
-
How to be more Literal in Python
The basic motivation behind them is that functions can have arguments that can only take a specific set of values, and those functions return values/types change based on that input. Common examples are (you can find more here):
-
Python 3.11.0b1 is out! Python 3.11 is now in feature freeze mode!
While yes 26 people liked the idea here: https://github.com/python/typing/issues/193
-
Type Hinting - Constrain metaclass of typing.Type
but looking at relevant issues on GitHub it seems this has been shot down repeatedly. python/typing#18, python/typing#213
-
What type hint should I use for "some container type" in general but explicitly exclude the str type?
See https://github.com/python/typing/issues/256 for a discussion.
-
Type annotations: how to express list contravariance?
Lower bounds are not supported for TypeVars, unfortunately.
-
I use attrs instead of pydantic
Mypy allows that because initial versions of PEP-484 allowed that. This has changed; here's the current wording on the PEP:
> This is no longer the recommended behavior. Type checkers should move towards requiring the optional type to be made explicit.
https://www.python.org/dev/peps/pep-0484/#id29
-
Can I walk through the entire hierarchy of object types?
Dunno, other, larger projects than the one I'm working on seem to run up against this from time to time. (rasa_core, to pick one example from near the top of a Google search; also Telethon, Blender, TensorFlow, Pandas. Guido also filed a bug on the typing module in an early version of Python 3.5 because of unexpected implications of this particular issue, so the problem isn't exactly purely theoretical.) That's aside from the wish for conceptual purity in the call signatures of classes and their subclasses, which is not always and automatically a bad wish to have; and the notion that a language that prides itself on its introspective faculties might want to make introspection of classes from the top of a class hierarchy possible, at least in theory? Perhaps to facility learning about the language and/or visualizing large class hierarchies easily, for instance?
unboxed
-
How can Haskell programmers tolerate Space Leaks?
With Lev as defined here.
-
[ANNOUNCE] GHC 9.2.1-rc1 is now available!
Check out unboxed. I think that could be a good starting point. I recently updated it to the 9.2.1 alpha here: https://github.com/noughtmare/unboxed/commit/b6338e68540a2c62a6aae6ded0dcdc3b83106916. I should check again if the this issue is fixed in this rc.
-
Principles of Programming Languages - Robert Harper
I tried it out and it is really not usable yet unfortunately. There are several problems. I think the main issue is that you need two versions of all functions and data types. And currently classes like Num are not levity-polymorphic (there is a proposal about this), so you can't use + to add two "real" inductive peano naturals. One problem with making type classes levity-polymorphic is that top-level bindings can't be levity-polymorphic, so mempty cannot be levity-polymorphic. A workaround is to use a type class to levitate levity-polymorphic variables, but that has disadvantages too. Levitated values are not shared and must be recomputed at every call site.
What are some alternatives?
mypy - Optional static typing for Python
bytestring - An efficient compact, immutable byte string type (both strict and lazy) suitable for binary or 8-bit character data.
pyre-check - Performant type-checking for python.
unboxed - experimenting with unlifted classes via backpack
fp-ts - Functional programming in TypeScript
pydantic - Data validation using Python type hints
Telethon - Pure Python 3 MTProto API Telegram client library, for bots too!
mashumaro - Fast and well tested serialization library
intellij-community - IntelliJ IDEA Community Edition & IntelliJ Platform
flask-parameter-validation - Get and validate all Flask input parameters with ease.
datamodel-code-generator - Pydantic model and dataclasses.dataclass generator for easy conversion of JSON, OpenAPI, JSON Schema, and YAML data sources.
pyannotate - Auto-generate PEP-484 annotations