Dear thrift developers, especially those with an interest on the Python side of Thrift,
In trying to add UUID support for Python I ran into a few build and CI related issues and decided to try and get those out of the way before continuing on this path. As such I have created a branch and PR for basic housekeeping and cleanup: https://github.com/apache/thrift/pull/3231 The PR description captures the gist of the changes there. I also ran into https://issues.apache.org/jira/browse/THRIFT-5885 and tried to implement a fix in https://github.com/apache/thrift/pull/3232. PS: The work here is built on top of the above mentioned PR thus the diff in GitHub is misleading. Given the Appveyor builds are using old versions of Python, as well as python tests not run in the GitHub actions (prior to #3231 above) I started looking at an Action for building and testing on Windows, the same parts currently done in Appveyor but using newer versions of relevant parts. This is ongoing and still in my thrift fork @ https://github.com/CJCombrink/thrift/pull/7. This work is probably related to https://issues.apache.org/jira/browse/THRIFT-5564 Apart from bringing attention to those PRs I would like some inputs regarding these efforts: 1. Should I create an issue for my "housekeeping" effort and branch and link against that? (Or Below) 2. Instead of above, abandon #3231 (Housekeeping PR) and only try to push through #3232 (Enum fix) since it already contains the housekeeping work? 3. Feedback regarding the Windows Action if possible, like where it would live, what it should include etc. Any input will be appreciated. Python is not my strong point thus would welcome any comments and support in this regard. Regards, Carel
