Prepare 3.13-compatible release

[youknowone]

Would it be ok? @lucas42 @cdce8p

distutils is not included because its test does not pass on 3.13

[lucas42]

Looks good to me!
Do you do the actual release process manually? I've not noticed any code in the repo for releasing.

[youknowone]

I built packages with update.py and manaully uploaded it using twine previously.
I am going to write a github workflow file for release this time.

[youknowone]

Let's target the release tomorrow.

[cdce8p]

Suggested change

	- name: Get folders with tests
	id: get-folders
	run: |
	FOLDERS=$(find . -maxdepth 2 -type d -name 'tests' ! -path '*/distutils/*' \
	| cut -d "/" -f2 | sort -u \
	| jq -Rsc 'split("\n") | map( select(length > 0) )')
	- name: Set up Python
	uses: actions/setup-python@v5
	with:
	python-version: "3.13"
	check-latest: true
	- name: Get folders with tests
	id: get-folders
	run: |
	pip install -U pip -r requirements_test.txt
	FOLDERS=$(python scripts/helper.py list-test-folders --exclude distutils)

[cdce8p]

Looks good overall! I did a quite more extensive test on my fork and the release was created successfully with all artifacts uploaded.

If you have configured Trusted Publisher in PyPI, I'd say go for it!

[cdce8p]

Suggested change

pull_request: # FIXME: temporary until release.yaml works

[youknowone]

I have to configure many packages in this repository for trusted publisher. I am trying to set token

[youknowone]

And thank you so much. This is my first time to setup PyPI release by workflow. It must had taken a lot more time without your help.

[youknowone]

The release action: https://github.com/youknowone/python-deadlib/actions/runs/11597133339

[cdce8p]

The release action: https://github.com/youknowone/python-deadlib/actions/runs/11597133339

Saw it just know. Unfortunately there is a small issue with standard-chunk. It wasn't uploaded to PyPI. Think I know why as well. Will open a PR shortly.

[youknowone]

I am not sure but I messed up something. it was actually released in https://github.com/youknowone/python-deadlib/actions/runs/11596984318/job/32289460524

And yeah, chunk doesn't have tests 😂

[cdce8p]

And yeah, chunk doesn't have tests 😂

Would have been too easy if it worked the first time 😄 Opened #38.

[youknowone]

@cdce8p @lucas42 Thank you so much, it would take a lot more time without your helps.

Please tell me if anyone of here be interested in this project ownership. Due to the project's motivation, I am a bit concerned about being the sole owner.

I’d love to share the responsibilities or even donate it to the Python or PyPA organizations one day, but based on PEP 594, that doesn’t seem likely to happen soon, if ever.

[lucas42]

@youknowone Yay, that's an amazing milestone! 🎉

It's been great working with you on this up until now. But I don't think I've much to contribute after this point. I'm not an expert in what any of these libraries are doing internally.
In fact, my main motivation this whole time was to be able to do this pull request on another library, which I'm using in a personal project: beetbox/audioread#145

I wish you all the best in future endeavours! 🙇

[cdce8p]

I'm in the same category as @lucas42 here, unfortunately. While I'm able to help out from time to time, my main intention was to get "a" working backport lib going so I can update another project for Python 3.13.

[youknowone]

Thank you for the replies. Yes, I will try to keep them up for a while, though I am not a kind of Python code writer anymore 😂
It was all the good experience with you. I also hope I don't need to publish a new version of them for a while. Probably the next release will be related to a new PEP deprecating more libraries.