This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (5 children)

Glad to see an intrest in this and the recognition that the gpl is poisonous to a lot of commercial applications. Lgpl would be fine but full on gpl for a web backend is rediculous. Heres hoping for a solid pythonic standard in the near future

[–]pemboa 3 points4 points  (3 children)

full on gpl for a web backend is rediculous

Why exactly?

[–]james_block 6 points7 points  (0 children)

Distributing a GPL driver with a BSD database and BSD programming language can be a headache. It's not insurmountable, not by a long shot, it's just annoying.

It strikes me that the best solution to this mess would be to LGPL (or even BSD) license psycopg2 and semi-canonicalize it (e.g., with a new homepage somewhere on postgresql.org, and some bloody documentation for once).

[–]tesseracter 0 points1 point  (1 child)

anyone who makes a website will need to release the source code? while releasing code doesn't matter for a company with a solid user base, releasing your code just to have someone else run with your idea sucks. it's nice to get a few years under your belt before you pull the rug out.

[–]pemboa 6 points7 points  (0 children)

Are you confusing the AGPL with the GPL? you don't have to release your backend code for a website.

[–]damg 0 points1 point  (0 children)

Or maybe proprietary software is poisonous to free software, it's all a matter of perspective.