* Package name    : python-chess-com-api
  Version         : 1.1.0
  Upstream Contact: Bryan Tran <bryan.tran.xyz@gmail.com>
* URL             : https://github.com/Stupidoodle/chess-com-api
* License         : Expat
  Programming Lang: Python
  Description     : Python wrapper for the Chess.com API

A modern, fully typed, asynchronous Python wrapper for the Chess.com API.

This is a dependency for home assistant. I intend to seek sponsorship and
maintain this package in the home assistant team.

Hi Edward & Thomas,

I prepared python-chess-com-api for home-assistant. Thomas sent me some review
notes, which I think I've remediated. During the course I had to make some more
changes to the docs package, which led to relatively more commits than I
anticipated, but hey.

Below is my follow up of all review notes. I think python-chess-com-api is
ready for more review or upload to NEW.

Br,

Pieter

Thomas, your comments were:

I've started using dgit on Edward's pointer. dgit has no separate upstream and
pristine-tar branches. You edit upstream directly on their main branch and dgit
keeps track of your patches by consolidating them in
debian/patches/dgit-changes.

This workflow is documented in dgit's man page dgit-maint-merge (7).

Done.

Ref above, I think that would break the dgit-maint-merge (7) flow. I've not
renamed the patch.

Thanks! That's a lot cleaner. I went for the PYBUILD_TEST_ARG= --ignore etc
pattern.

Dear Mentors,

I've packaged the Python Chess.com API package as a dependency for home
assistant.

The package already received some review notes from zigo, which I've followed
up. These are visible in the RFS bug #1147714.

This lib is packaged using the dgit-maint-merge(7) flow and instructions on
how I can hand this over as a sponsee and how to follow this up as a sponsor
are in dgit-sponsorship(7) SPONSEE WORKFLOW and SPONSOR WORKFLOW respectively.

The package source is currently in salsa at
https://salsa.debian.org/homeassistant-team/deps/python-chess-com-api

You can generate an orig tarball using the `git deborig` command.

Patches are commits on the main branch and are managed by dgit when a new
release is merged. Please refer to dgit-maint-merge(7) and the explanation in
the debian/patches directory.

After your review, if you consider the package okay to upload, you can build
the package with `dgit -wgf sbuild -A -C` and push the binary package using
`dgit -wgf push-built`, per dgit-sponsorship(7).

Thanks,

Pieter