Skip to content

Please clarify the actual license #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
hroncok opened this issue Feb 12, 2019 · 6 comments
Closed

Please clarify the actual license #37

hroncok opened this issue Feb 12, 2019 · 6 comments
Assignees

Comments

@hroncok
Copy link
Contributor

hroncok commented Feb 12, 2019

The LICENSE file lists 2 licenses. A BSD-like one and also PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2. Do I choose freely? Are some bits licensed under BSD and other bits under PSF? Which bits?

setup.py has:

    license="BSD",

and

    'License :: OSI Approved :: BSD License',

Thanks for clarifying.

@simonpercivall simonpercivall self-assigned this Feb 12, 2019
@PatrikKopkan
Copy link

Hi,
Maybe I can help determining the right licence.
It seems that you'd like code you wrote to be under BSD (so anyone can use it), but some bits are from Python so they need the Python licence. Is that right?

@hroncok
Copy link
Contributor Author

hroncok commented Mar 11, 2019

@simonpercivall I want to include your package in Fedora and this is blocking me. We are very careful about licenses. Could you please clarify? Thank You.

@simonpercivall
Copy link
Owner

simonpercivall commented Mar 11, 2019 via email

@QuLogic
Copy link

QuLogic commented Mar 17, 2019

Isn't this explained in the readme?

This library uses mature and core maintained code instead of trying to patch existing libraries. The unparse and the test_unparse modules are under the PSF license.

@hroncok
Copy link
Contributor Author

hroncok commented May 29, 2019

Sorry about the noise.

@hroncok hroncok closed this as completed May 29, 2019
@TTMaZa
Copy link

TTMaZa commented Jul 27, 2021

Hi there. We stumpled upon the same question. I've made a suggestions, that clearly brings out this "Dual" Licensing:

#64

Best regards
Manuel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants