Changes between Initial Version and Version 1 of Ticket #26511, comment 42


Ignore:
Timestamp:
03/09/22 02:54:30 (5 months ago)
Author:
gh-tkralphs
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #26511, comment 42

    initial v1  
    33If you think about the philosophical underpinnings, what the GPL tries to prevent is that I modify the source code of a GPL'd code (or something linked to a GPL'd code) and then re-distribute it only in binary form, thereby profiting from a work that is derived from a GPL'd work, but not sharing the source of that derived work. The viral nature is just meant to try to ensure that everyone plays by these rules to the extent possible by preventing anyone from linking to GPL'd code in binary form without playing by the rules. But unless you distribute only a .pyc file and not a .py, this simply can't happen in Python. Although it would be possible to distribute a Python package in byte-compiled form without source (or even in some obfuscated form of source), this is not what you would be planning to do and it just doesn't run afoul of the GPL, either by the letter of the law or in spirit.
    44
    5 Of course, as always, I am not a lawyer, but in my opinions, you can take python-mip, modify it as you wish, and re-distribute the modified version as an integrated part of Sage without any license issues. Here is an answer on Open Source Stack Exchange that I think is correct, although everyone seems to miss the point and disagree.
     5Of course, I am not a lawyer, but in my opinion, you can take python-mip, modify it as you wish, and re-distribute the modified version as an integrated part of Sage without any license issues. Here is an answer on Open Source Stack Exchange that I think is correct and supports this point of view, although everyone else seems to miss the point and disagree.
    66
    77https://opensource.stackexchange.com/a/8472