Jens Tröger

Finding Python types for Columns

1

Hi, thanks for this function just as I started putting together one of my own. Regarding this code: https://github.com/tiangolo/pydantic-sqlalchemy/blob/8667e213a6ad8e62288fad2a6621958e8ab0b688/pydantic_sqlalchemy/main.py#L24-L30 Have you looked at the [typing.get_type_hints()](https://docs.python.org/3/library/typing.html#typing.get_type_hints) function? Perhaps ```python else: python_types...

feat: add support for Python 3.12

3

@behnazh I’ve not yet dropped support for Python 3.10 because we’re using it in other projects. Also, I noticed that Dependabot — when checking for package updates — doesn’t consider...

Add pre-release support

4

## Currently The release workflows support only [final releases](https://peps.python.org/pep-0440/#final-releases) of a package, and no [pre-releases](https://peps.python.org/pep-0440/#pre-releases). The branches support these release workflows by PR → `staging` branch → `main` branch, where...

There are differences between [YAML 1.1](https://yaml.org/spec/1.1/) and [YAML 1.2](https://yaml.org/spec/1.2.2/), and out there in the wild different tools use different YAML parsers for either version of YAML files. Currently, we use...

Consider code complexity tracking, and other tools.

10

Tools like [Wily](https://wily.readthedocs.io/) and [Radon](https://radon.readthedocs.io/) allow to track code complexity metrics, e.g. based on [cyclomatic complexity](https://en.wikipedia.org/wiki/Cyclomatic_complexity) or [Halstaed’s complexity metrics](https://en.wikipedia.org/wiki/Halstead_complexity_measures). It might make sense to track these (and other?) metrics...

If that file is missing then https://github.com/jenstroeger/python-package-template/blob/40e438b0adab9e4d90f754811bba7a1284d592d9/.github/workflows/sync-with-upstream.yaml#L49-L50 sets `CURRENT_VERSION` to `"v0.0.0"` such that https://github.com/jenstroeger/python-package-template/blob/40e438b0adab9e4d90f754811bba7a1284d592d9/.github/workflows/sync-with-upstream.yaml#L66 results in an error: ``` fatal: ambiguous argument 'v0.0.0..v2.8.0': unknown revision or path not in the...

> would it make sense to check if a branch for that previous version exists, and close the PR and delete that now older branch? Or, if not, mark the...