3 ms·
That seems like a way to kill pypi as a popular service. For the 3 or so packages I have, I'd probably just change the description to pull from another location
by viraptor 3y ago
That seems like a way to kill pypi as a popular service. For the 3 or so packages I have, I'd probably just change the description to pull from another location rather than pypi. It's not that I can't afford it, it's just that I don't want to end up paying for another subscription if rules change.
There are also people who wouldn't be able to pay for legal reasons. It would also stop teenagers who don't need the hassle of getting parents to pay.
- wombatpm 3y agoI think you misinterpreted the comment. The Payment would be required for people wanting to PUSH to pypi. Developers and people PULLING from pypi would remain free. The problem is garbage and malicious submissions.
- chatmasta 3y agoI don't think the comment you're replying to misunderstood the comment. I think the author was saying that they would update the readme of their projects (which they _push_ to a registry, and for which they do not want to pay) to instruct people to pull the package from somewhere else.
- wombatpm 3y agoYou can do that, but it certainly doesn’t help you with project discovery. If you want only distribute via GitHub that’s fine. But as a developer I’d need a compelling reason to use such a project vs one distributed via pypi
- viraptor 3y agoThat's ok. Many projects don't care about discovery. (As in being popular/brand name, rather than being possible to find if someone needs that specific thing) And even those that do can rely on people searching for "python package for frobnicating" and finding it somewhere else. I'm publishing my code for the benefit of others, not mine, so if someone writes the same thing and pays to get it published, that's fine with me. > I’d need a compelling reason to use such a project vs one distributed via pypi Apart from trivial projects, there's not that many alternatives you can swap out. Your choices may be "use such project or write your own".
- Too 3y agoTbh, changing PyPi urls to git urls at GitHub would almost be a win-win. At least GitHub has namespaces and many other indicators of trust, such as issue tracker, stars, git log and so on. You would loose semver however. Usually checking the official GitHub projects readme for exact name of pip install command is what I normally do anyway. I would never ever use PyPi as a discovery mechanism, it has too many typosquatters and other lookalikes.
- matheusmoreira 3y agoImagine having to pay to give open source software away for free. Sounds like a great way to ensure the death of PyPI.
- dalke 3y agoI already host my own packages on my own domain. It was not hard to make a PEP 503 "simple" index. python -m pip install chemfp -i https://chemfp.com/packages/ This is commercial/proprietary software for cheminformatics fingerprints. I don't feel comfortable hosting it on PyPI as I suspect in the future they will want to pay to host non-FOSS licensed software. Which is definitely their prerogative! By hosting it myself already I end up with less lock-in. Having done it both way, hosting the packages myself means I also like having full access to the download logs, the ability to replace files when I made a mistake, and I can rsync using my usual SSH keys instead of using PyPI's API token system to upload wheels. I have a very old version of my software on PyPI, distributed under a free software license. The major downside is that people sometimes download that instead of the most recent version. But since it doesn't work on Python 3.x, they either search and find my web site, with the download instructions, or email me. I figure I also have keep something on PyPI, to prevent name squatting.
- EVa5I7bHFq9mnYK 3y agoHow about assigning a trust level to each package. Level 0 - Free, unchecked package, Level 1 - reviewed by at least one moderator, Level 2 - developer bought a $100 license + reviewed, etc. Then it's up to package consumer to decide which package they trust.