Re: PyPi again
I can probably add you to the PyPi maintainer list. Would that help? Am 12.01.2024 um 23:19 schrieb Yuxuan Wang: IMHO there are two issues with the pypi publishing problem: technical and non-technical. The non-technical issue is the credential/secret required to publish to https://pypi.org/project/thrift/. Any of the technical solution also depends on that being available. Once we have it (in github actions secret store, for example), then technical solution is not the hard part. As I mentioned in the jira thread Reddit already has a github action pipeline to publish to pypi on git tag we can upstream to thrift project to be used (so whenever a maintainer pushes a tag to github, github actions auto publishes to pypi). Or others can contribute other solutions. On Sat, Jan 6, 2024 at 3:18 AM Jens Geyer wrote: @all, I just want to bring up that topic again. There is a rather frequent stream of (absolutely legitimate) questions regarding the PyPi packages not being published. So it seems fair to say that there is obviously a certain demand within the community, which is super great. Now on the other hand we have no noteworthy reactions from that very same community to help with that topic. Let me put it bluntly. This is not your mothers supermarked where stock refills almost like automagically overnight. This is open source. It works as long as there are at least some people spending parts of their valuable time supporting projects. It is about giving & taking. Thrift supports about 20+ target languages. So it is fair to say that supporting packages for all of them (where approprate) is quite a bit of work. Of course I can only speak for myself, but I personally maintain quite a number of packages after each release. Thanks to the great work of other people (e.g. @JimKing) who spent their time on that topic before me, this became manageable by setting up and documenting a well-defined process to follow which also does not eat too much additional release time. If we can have such a process for PyPi that would be super awesome. Right now this is not the case, unfortunately. This is where you could chime in. See also https://protect.checkpoint.com/v2/___https://github.com/apache/thrift/pull/2555___.YzJ1OnJlZGRpdDpjOmc6ZGEyMWNiMjExZDEwMWVjZmIzNGI3MWIzMGFmMmEyZTY6Njo0ZDRjOmIyMTFmOWI4ODI2ZTJmZTIxMTQ0NmNhMmQ4M2I5M2EzNDBhY2VhOTVlOGE2YzVjZDgyNWZlMGVmZmZhMThhOWU6cDpU Happy New Year everybody, JensG
Re: Contribute to an issue - THRIFT-5688
Hi, yes I do have PyPi creds. What would bve the optimum would be some sort of a step-by-step process description that someone can follow, even with little to no clue about Python and/or its packaging system. We have a docuement which also has a small section abpout 3rd party package managers at the very end. If its more than a few bullet points consider putting it into some extra *.md and link to it from there. https://github.com/apache/thrift/blob/master/doc/ReleaseManagement.md#third-party-package-managers If you send a PR, the I can test the process and we can work it out together until we are all happy with it. Have fun, JensG From: Adheeth P Praveen Sent: Sunday, December 17, 2023 4:57 PM To: dev@thrift.apache.org Subject: Re: Contribute to an issue - THRIFT-5688 Hey Jens Thank You for the reply and being positive! I took a manual approaching to the packaging process initially. I've used the source package available from http://archive.apache.org/dist/thrift/0.19.0/thrift-0.19.0.tar.gz and I've been able to generate a python package from it. I've also done a local install on the built package and it worked without any issues. For generating auto build there's a bit I need to learn and explore - mainly pipelines. For uploading the package to the PyPi repo we'll need access to the repository and make use a utility called twine. I believe you do have the credentials/access and you'll be able to do this process. If not, you'll have to add a maintainer. How should i go about it from here? Where should i share the built packages? Do we need a GitHub issue on this? If Yes, any pointers on how to create one? Regards, bull500 From: Jens Geyer Sent: Thursday, November 30, 2023 7:28 PM To: dev@thrift.apache.org Subject: Re: Contribute to an issue - THRIFT-5688 Hi Adheeth, > I'm not sure if this is the right place to ask this Welcome! Yes, indeed it is. but the JIRA and GitHub looked very specific to development purpose than discussions Correct. General matters are to be discussed in these mailing lists. > I came across this issue and I wanted to contribute towards addressing the problem. As the ticket says, we currently have the funny situation that there is a high demand for updated python packages but nobody that wants to do this or can spare the time. I myself do quite a number of packages myself but Thrift supports about 20+ target languages - most of which come with an associated library package. So any help on this is highly appreciated! So where are we with that ticket and where do we want to go? As shortly noted in the ticket, what we want is some step by step process that one can follow to publish the pypi package even though one never did that before nor has any intention to follow overly complex procedures (as these tend to break over time). What we have already is an pull request with an updated pypi publishing procedere, but since I do not use Python myself I can't say much about the status of it. https://github.com/apache/thrift/pull/2555 As a first milestone it would be perfect if we could publish the latest package in _some_ way (even manually) in order to satisfy the demand for it. > I'm new to packaging a project to pypi but i would like to help and learn during the process. Learning for sure is a by-product of working in the FOSS community. Therefore, people around are usually keen to help on specific questions, especially if those are related to the Apache Thrift project. What we cannot provide is countless hours of help to guide contributors through the basics of a certain field. There are much better places for this, and in this particular case I'm sure the Python community would be of a much greater help. Have fun, JensG Am 25.11.2023 um 18:34 schrieb Adheeth P Praveen: Hello, I came across this issue and I wanted to contribute towards addressing the problem. https://issues.apache.org/jira/browse/THRIFT-5688 I'm not sure if this is the right place to ask this but the JIRA and GitHub looked very specific to development purpose than discussions I'm new to packaging a project to pypi but i would like to help and learn during the process. Are there any prerequisites I need to do/learn before addressing this issue? I would like to have some support if I hit some technical snags if it comes to a point where I'm unable solve on my own. Thanks for reading this! bull500
Re: Contribute to an issue - THRIFT-5688
Hey Jens! Have you had the time to go through my previous post on THRIFT-5688 (python packaging) on the mailing list? I had made some progress but I'd like your thoughts and opinions before moving foward. Thanks for the time Thanks bull500 From: Adheeth P Praveen Sent: Sunday, December 17, 2023 4:57 PM To: dev@thrift.apache.org Subject: Re: Contribute to an issue - THRIFT-5688 Hey Jens Thank You for the reply and being positive! I took a manual approaching to the packaging process initially. I've used the source package available from http://archive.apache.org/dist/thrift/0.19.0/thrift-0.19.0.tar.gz and I've been able to generate a python package from it. I've also done a local install on the built package and it worked without any issues. For generating auto build there's a bit I need to learn and explore - mainly pipelines. For uploading the package to the PyPi repo we'll need access to the repository and make use a utility called twine. I believe you do have the credentials/access and you'll be able to do this process. If not, you'll have to add a maintainer. How should i go about it from here? Where should i share the built packages? Do we need a GitHub issue on this? If Yes, any pointers on how to create one? Regards, bull500 From: Jens Geyer Sent: Thursday, November 30, 2023 7:28 PM To: dev@thrift.apache.org Subject: Re: Contribute to an issue - THRIFT-5688 Hi Adheeth, > I'm not sure if this is the right place to ask this Welcome! Yes, indeed it is. > but the JIRA and GitHub looked very specific to development purpose than > discussions Correct. General matters are to be discussed in these mailing lists. > I came across this issue and I wanted to contribute towards addressing the problem. As the ticket says, we currently have the funny situation that there is a high demand for updated python packages but nobody that wants to do this or can spare the time. I myself do quite a number of packages myself but Thrift supports about 20+ target languages - most of which come with an associated library package. So any help on this is highly appreciated! So where are we with that ticket and where do we want to go? As shortly noted in the ticket, what we want is some step by step process that one can follow to publish the pypi package even though one never did that before nor has any intention to follow overly complex procedures (as these tend to break over time). What we have already is an pull request with an updated pypi publishing procedere, but since I do not use Python myself I can't say much about the status of it. https://github.com/apache/thrift/pull/2555 As a first milestone it would be perfect if we could publish the latest package in _some_ way (even manually) in order to satisfy the demand for it. > I'm new to packaging a project to pypi but i would like to help and learn during the process. Learning for sure is a by-product of working in the FOSS community. Therefore, people around are usually keen to help on specific questions, especially if those are related to the Apache Thrift project. What we cannot provide is countless hours of help to guide contributors through the basics of a certain field. There are much better places for this, and in this particular case I'm sure the Python community would be of a much greater help. Have fun, JensG Am 25.11.2023 um 18:34 schrieb Adheeth P Praveen: > Hello, > > I came across this issue and I wanted to contribute towards addressing the > problem. > https://issues.apache.org/jira/browse/THRIFT-5688 > I'm not sure if this is the right place to ask this but the JIRA and GitHub > looked very specific to development purpose than discussions > > I'm new to packaging a project to pypi but i would like to help and learn > during the process. > Are there any prerequisites I need to do/learn before addressing this issue? > I would like to have some support if I hit some technical snags if it comes > to a point where I'm unable solve on my own. > > Thanks for reading this! > bull500 >
