5 ms·
I understand the argument that they might not want to stay on Python so they want to get people used to downloading from their zip instead of PyPi. But why not
by gurchik 5y ago
I understand the argument that they might not want to stay on Python so they want to get people used to downloading from their zip instead of PyPi. But why not provide an rpm or deb? I don't understand why the only two official options are PyPi or downloading a zip and running the installer.
- lazypenguin 5y agoThe last comment from Amazon before they locked the thread mentions they are putting together more packaging options.
- gurchik 5y agoYou're right, I missed that, thanks.
- notatoad 5y ago@joguSD's second comment, preceding most of the discussion, also mentions that they're looking to get it into brew and linux package managers
- nonameiguess 5y agoAfter a year and a half, they claimed to be prioritizing this for Q2, which seemingly ended last month, and they still haven't offered anything. Heck, there's people on the thread offering them build scripts that will create debs and rpms for them. It isn't that hard to do. I can understand why they don't give a crap, though. The people responsible for setting up recipes to build and deploy a few thousand servers with AWS tooling on them that would sure like to be able to automate updates of the packages aren't the ones forcing their companies to use AWS, so Amazon prioritizes meeting the needs of the people making purchasing decisions rather than the people who actually have to use the tooling. With enough vendor lock-in and long term contracts already signed, they don't need to care about improving user experience to come up to par with system maintainer expectations from the early 90s.
- deleted 5y ago[deleted]