zbentley commented on issue #11203: URL: https://github.com/apache/pulsar/issues/11203#issuecomment-890046478
@sijie and @aahmed-se , something that may add a little more color to this issue: the Pulsar Python client library is very hard to build from source, so having working wheels is unusually important for folks who want to talk to Pulsar from Python. To wit: neither I nor any of my coworkers, with workstations across several years' worth of OSX editions and Linux distros, have been able to effectively build this package from source on our first try. On our production servers we eventually got a build that worked, but our workstations--especially our OSX ones--remain on various editions because of the difficulty satisfying different constellations of OpenSSL/grpc/zlip/etc. dependencies. This isn't uniquely a Pulsar issue--Python packages with compiled components are just notoriously awful to build on OSX in general, and the fault for that lies with the ecosystem, not this project in any way--but it is within the Pulsar maintainers' ability to easily fix by providing a range of working binary wheels so folks don't have to BFS. This is complicated by the fact that folks often need versions built against many different combinations of (python version, OS version, library version). For example, I was able to get 2.8.0 BFS working on my Mac against 3.7.7 in an hour of fiddling/environment setup, but python 3.9 and higher hit inscrutable compilation issues in transitive dependencies pretty quickly. I am happy to volunteer a day or two of my time to build wheels on various OSX versions (I run a few in virtual machines) and supply them, or the steps to build them, if that would help. Anything I can do here? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
