gpgmepy issues and issue tracking

[Ingo Klöcker]

On Donnerstag, 7. August 2025 14:08:28 Mitteleuropäische Sommerzeit Paul 
Schwabauer via Gnupg-devel wrote:
> 1. Beta Version Numbering
> 
> When building gpgmepy, the version generated is 2.0.1, without a beta 
> suffix. I followed the documented process for incrementing the version, 
> but unlike with 2.0.0, the beta version is not being generated based on 
> the number of commits. This complicates pushing out beta releases that 
> include minor changes and require user feedback.
> 
>    - Does a different tag need to be used?

Yes. You have to create an annotated tag. Ideally, you create a GPG-signed 
tag.

> 3. Documentation and Example Scripts on PyPI
> 
> The release tarball includes several Python examples, which are no 
> longer (correctly) included in the source distribution package on PyPI. 
> However, this makes it difficult for users to discover or access them.
> 
> We need to discuss:
> 
>    - Where to host or link these example scripts
> 
>    - Whether to include references to them in the PyPI package 
> description or elsewhere

I don't know what's common in the Python world. I would look for examples in 
the Examples section of the official documentation. Given that there doesn't 
seem to be documentation published anywhere linking them from the description 
makes sense. The scripts are hosted in the repo.

Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20250808/ae486297/attachment.sig>