Skip to content

Conversation

@NickBorgers
Copy link

This project cannot currently be used in other work because no license has been defined. I would really like to use it in a project, and am proposing MIT license if that would align with your desires @coburnw.

@coburnw
Copy link
Owner

coburnw commented Jul 20, 2020

Hi Nick,

Each file integral to the library that i wrote should already be prefaced with an mit license statement. I clipped vxi11.py, written by Alex Forencich, from his python-vxi11 client which i believe is an mit license. However i didnt write rpc.py and it wasnt clear to me what license it was published with.

If you wanted to do some sleuthing, either determining what license rpc.py should fall under or what we could replace it with, i'd be interested.

@NickBorgers
Copy link
Author

NickBorgers commented Jul 30, 2020

@coburnw
At this point I think this is overall the LICENSE file under which rpc.py is governed: http://svn.python.org/projects/python/trunk/LICENSE
However, there are at least two complexities I see:

I will dig deeper when I have more time; I agree this is fuzzy.

I think looking for an alternative implementation is probably a wise course, that is probably what I will do.

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

Successfully merging this pull request may close these issues.

2 participants