-
I was a little too fast and created some stubs for the [typeshed project](https://github.com/python/typeshed) in order to allow for type checking code using this library according to [PEP 561](https:/…
-
I'm packaging your module as an rpm package so I'm using the typical PEP517 based build, install and test cycle used on building packages from non-root account.
- `python3 -sBm build -w --no-isolatio…
-
### Feature description
Add a static type checker like [`mypy`](https://mypy-lang.org/) to our lint workflows. Note that this doesn't mean that we have to declare support for [PEP561](https://peps.py…
-
# Pyre Bug
**Bug description**
A previously working configuration of pyre has started mysteriously failing with the following error:
```
ƛ Pyre encountered an internal exception.
ƛ Raised at …
-
```
=================================== FAILURES ===================================
_____________________________ test_coerce_hint_any _____________________________
def test_coerce_hint_any(…
-
You went through the trouble of typing your package - adding a py.typed file to it will help type analysis.
-
The [typeshed repository](https://github.com/python/typeshed) is certainly *the* right place where to put those types. Why not submitting the project to them?
-
#### Is your feature request related to a problem?
I want to have type stubs when using geopandas
https://typing.readthedocs.io/en/latest/source/stubs.html
#### Describe the solution you'd li…
-
## Driver version
## Redshift version
## Client Operating System
## Python version
## Table schema
## Problem description
It looks like this package has type annotations fu…
-
# Pysa Bug
**Pre-submission checklist**
[+] I've checked the list of [common issues](https://pyre-check.org/docs/pysa-quickstart/#common-issues) and mine does not appear
**Bug description**
Th…