Previously LGPL, now re-licensed as closed-source/commercial. Previous code taken down.
Commercial users pay $99/year, free for personal use but each user has to make a free account after a trial period.
Previously LGPL, now re-licensed as closed-source/commercial. Previous code taken down.
Commercial users pay $99/year, free for personal use but each user has to make a free account after a trial period.
Does pip really allow binary blobs? That effectively makes it zero security.
To be fair it has some valid use cases, take ruff for example.
But pip/pypi does not have any proper security at all, and just blocking binary blobs wouldn’t make a difference when you can freely execute any python code during installation - Much like downloading an executable from any site online, you are expected to make sure you can trust whoever uploaded what you are downloading. You could say the same about other sites like GitHub too.
There is a fair difference still between source available and binary blob. The blob has essentially no chance of ever being audited.
binary blobs aren’t really a security hole , since AFAIK the pypi team don’t check every package for malicious code before they get shown publicly . it just shifts the trust from pypi to the library authors
Take a look at the Source Distribution files: https://pypi.org/project/PySimpleGUI/#files
As far as I can see, it’s still all just Python.