Python

6331 readers

313 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

📅 Events

Past

November 2023

PyCon Ireland 2023, 11-12th
PyData Tel Aviv 2023 14th

October 2023

PyConES Canarias 2023, 6-8th
DjangoCon US 2023, 16-20th (!django 💬)

July 2023

PyDelhi Meetup, 2nd
PyCon Israel, 4-5th
DFW Pythoneers, 6th
Django Girls Abraka, 6-7th
SciPy 2023 10-16th, Austin
IndyPy, 11th
Leipzig Python User Group, 11th
Austin Python, 12th
EuroPython 2023, 17-23rd
Austin Python: Evening of Coding, 18th
PyHEP.dev 2023 - "Python in HEP" Developer's Workshop, 25th

August 2023

PyLadies Dublin, 15th
EuroSciPy 2023, 14-18th

September 2023

PyData Amsterdam, 14-16th
PyCon UK, 22nd - 25th

🐍 Python project:

💓 Python Community:

#python IRC for general questions
#python-dev IRC for CPython developers
PySlackers Slack channel
Python Discord server
Python Weekly newsletters
Mailing lists
Forum

✨ Python Ecosystem:

🌌 Fediverse

Communities

#python on Mastodon
c/django on programming.dev
c/pythorhead on lemmy.dbzer0.com

Projects

Pythörhead: a Python library for interacting with Lemmy
Plemmy: a Python package for accessing the Lemmy API
pylemmy pylemmy enables simple access to Lemmy's API with Python
mastodon.py, a Python wrapper for the Mastodon API

Feeds

founded 1 year ago

MODERATORS

[email protected]

146

PySimpleGUI is now closed-source (github.com)

submitted 8 months ago* (last edited 8 months ago) by [email protected] to c/[email protected]

69 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 5 points 8 months ago (1 children)

This is so sad. I'm especially bothered about the force push to change history. This was a great library. Now I guess it's time to either use the fork or find something else.

[–] [email protected] 4 points 8 months ago (1 children)

The history change was probably to avoid violating the LGPL. If any contributors don't agree with the change (or you don't want to do the onerous task of getting consensus as required) you should remove their contributions from the work you make closed source as the contributions still come under LGPL until the original author consents to the change.

Or at least that's what people said here.

[–] [email protected] 4 points 8 months ago

That's incorrect in that you have to remove the contributions from source code or get permission. Rewriting git history doesn't get permission or remove history. It just hides it.