distutils has been deprecated in Python 3.10

[tirkarthi]

https://www.python.org/dev/peps/pep-0632/#migration-advice

django-ses/setup.py

Line 8 in 280ec80

from distutils.util import convert_path

Probably this code snippet could be vendored

https://github.com/python/cpython/blob/f4c03484da59049eb62a9bf7777b963e2267d187/Lib/distutils/util.py#L110

[pcraciunoiu]

@tirkarthi if you'd like to submit a PR with details and a proposed fix, I can review it.

[mlissner]

I briefly studied the setup.py file. I could be off base, but my impression is that there's a fair bit of boiler plate in there that could be reduced or removed by moving to more modern packaging.

For the packages my organization maintains, we usually use poetry, which does away with the setup.py and requirements.txt files and replaces them with a pyproject.toml file that holds all the needed metadata for the package.

I know I'm pushing for another big swap in #182, so maybe I'm becoming a bit of a gadfly, but if you'd welcome a switch to poetry, I think I'd be able to put together a PR for it and I think it'd be a nice leap forward for the project.

For example, building and uploading a package to pypi is much simpler. It's just:

poetry publish --build

This Github Action would do it on any commit tagged with v*..:

name: PyPI
on:
  push:
    tags:
      - v*.*.*
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Install Poetry
        uses: snok/install-poetry@v1.1.0
        with:
          virtualenvs-create: true
          virtualenvs-in-project: true
      - name: Publish to pypi
        run: poetry publish --build
        env:
          POETRY_PYPI_TOKEN_PYPI: "${{ secrets.pypi_token }}"

[pcraciunoiu]

@mlissner that sounds good to me. I've used poetry before and just haven't put in the time to switch this project. If you would do that, that'd be great. And nice to have publishing to pypi via CI too.