Declare support for Python3.12

[g-as]

• pylint doesn't work because v2.17.3 won't install on 3.12
• updated pylint to 3.3, I ignored some warnings, and left some others that need proper addressing
• updated pylint to ~3.2 (latest to be run with 3.8), I ignored some warnings in the conf file, and ignored the rest (possibly-used-before-assignment) in situ.
• pyspark doesn't support 3.12 as of 3.5.4, will do in 4.0. It crashes on import when it tries to import distutils. But besides that, it works. As suggested, I excluded 3.12 x pyspark from the matrix.

[codecov]

Codecov Report

Attention: Patch coverage is 83.33333% with 3 lines in your changes missing coverage. Please review.

Project coverage is 93.37%. Comparing base (812b2a8) to head (82c81de).
Report is 237 commits behind head on main.

Files with missing lines	Patch %	Lines
pandera/api/pyspark/container.py	87.50%	1 Missing ⚠️
pandera/typing/geopandas.py	0.00%	1 Missing ⚠️
pandera/typing/pandas.py	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1897      +/-   ##
==========================================
- Coverage   94.28%   93.37%   -0.91%     
==========================================
  Files          91      121      +30     
  Lines        7013     9365    +2352     
==========================================
+ Hits         6612     8745    +2133     
- Misses        401      620     +219     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[cosmicBboy]

thanks @g-as ! been wanting to do this for a while, thanks for taking the initiative on this.

pyspark doesn't support 3.12 as of 3.5.4, will do in 4.0

We can add exceptions in the CI workflow to only run pyspark on 3.12 for pyspark 4.0

[g-as]

Hi @cosmicBboy!

Excluded pyspark x 3.12 from the matrix as you suggested.

I ignored the rest of the pylint warnings so linters should pass (and thus tests should run). I'll let you decide on how you want to address those.

[g-as]

Hi @cosmicBboy,

as you've seen, the linting workflow fails for 3.12 because setuptools is missing from the environment.

I think it is related to this.

I thus added setuptools in the installed deps in the lint workflow.

[g-as]

Hi @cosmicBboy

I also added setuptools to the list of deps, since it is needed to run the tests

Hopefully everything will run now.

[g-as]

Yay \o/

What do you want to do about the coverage?

[cosmicBboy]

The coverage on this project has consistently been finicky, will address that in a seperate PR. In the mean time let's go ahead and merge this.

[cosmicBboy]

Thanks for the contribution @g-as ! and congrats on your first PR to pandera 🚀

[g-as]

Thanks!

Are you interested in me adding 3.13 support? Removing 3.8?

[cosmicBboy]

@g-as thanks for the effort!

Re: 3.8, let's go ahead and sunset 3.8 (since it's eol'd for a few months now)

Re: 3.13+ support, 3.13 and 3.14 has introduced breaking changes to runtime type checkers. For context, see:

• The First Annual Meeting of the Extraordinary League of Runtime Typers beartype/beartype#335 (python 3.13)
• The Second Annual Meeting of the Extraordinary League of Runtime Typers beartype/beartype#479 (python 3.14)

Besides being an entertaining read, it does provide a path forward for what library maintainers will have to do to address the breaking changes. Would you mind opening tickets for supporting 3.13 and 3.14?