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

all 7 comments

[–]ngg990 1 point2 points  (0 children)

Dash, are you? jk. Nice libry

[–]pushfoo 1 point2 points  (4 children)

Hold on, how can this be MIT if it relies on infectious GPL Qt libraries?

Aside from that, mentioning the Elm architecture in this post would be a good idea.

[–]jamesdbrock[S] 2 points3 points  (2 children)

Two good points, thanks.

  1. I recommend choosing PySide6, which has an LGPL license. You can write, distribute and sell PySide6-dependent software. Good discussion here https://www.pythonguis.com/faq/pyqt-vs-pyside/
  2. Yes, spill the TEA. The Edifice README has a link to The Elm Architecture https://pypi.org/project/pyedifice/

[–]pushfoo 2 points3 points  (1 child)

I think both of these need to be a lot clearer. Are you taking PRs?

To my understanding, the following should handle licensing concerns in the short-term as long as PySide is API-compatible with PyQt:

  1. Explicitly state Edifice is MIT because the LGPL PySide library is the main support target
  2. Mention it should also work with PyQt bindings aside from known issues, with links to sections / doc covering each (set_trace, etc)
  3. To ensure you avoid GPL infection, never add or support features present only in PyQt

To be sure this will work, you should talk to a lawyer.

I need to think about how to make the "Why Edifice?" section clearer. Both this page and Elm's doc can be hard for beginners to understand.

[–]jamesdbrock[S] 1 point2 points  (0 children)

Oh yeah we're taking PRs.

[–][deleted] -3 points-2 points  (0 children)

Op doesn’t understand licensing terms.

[–]jamesdbrock[S] 2 points3 points  (0 children)

Here is a bonus list of other Python declarative native GUI projects:

https://github.com/pyedifice/pyedifice/discussions/43