TW

Interestingly, installing pyqt6 on macOS M1 just works (unlike pyqt5): ``` (qt-testing) tw@mba2020 ~ % pip install pyqt6 Collecting pyqt6 Downloading PyQt6-6.4.2-cp37-abi3-macosx_10_14_universal2.whl (11.6 MB) |████████████████████████████████| 11.6 MB 30.3 MB/s Collecting...

i could contribute this after next release, if wanted.

I just tried on cygwin (on Windows 10): `platformdirs.user_config_dir() == '/home/admin/.config'` After setting `XDG_CONFIG_HOME=/home/admin/.config2` it adapted accordingly. So it seems to work as expected for cygwin, a platform imitating posix...

docs: this should be part of release checklist.

For borgbackup, I sign releases with gpg and upload the signature (together with the file I uploaded to pypi.org) to **github releases**. **pypi** does not support uploading gpg signatures any...

The idea is now to: - publish releases on "github releases" page, upload the sdist .tgz and the .tgz.asc signature - use twine to upload the same .tgz to pypi...

@RogerHaase I can do that, but mid term it would be good to also have another one or two developers who can make (preferably signed) releases.

Normal users should usually just do `pip install "moin==2.0.0a1"`, so pip fetches the stuff from pypi. That doesn't support GPG signature verification as pip and pypi do not support that....

@RogerHaase We should add the gpg key fingerprints (of the keys used to sign releases) to the docs. ``` % gpg --fingerprint [email protected] pub rsa4096/9F88FB52FAF7B393 2009-12-25 [SC] Key fingerprint =...

Without your pub key, one can not verify your signature: ``` % gpg --verify moin-2.0.0a1.tar.gz.asc gpg: assuming signed data in 'moin-2.0.0a1.tar.gz' gpg: Signature made Mi 27 Mär 21:54:41 2024 CET...