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
[WIP] Clean up of FlsaModel: fixing bugs + formatting + efficiency #3437
base: develop
Are you sure you want to change the base?
Conversation
CC @ERijck are you able to continue and finish this up? All the points above, plus all the |
@piskvorky yes, I will do that. |
Finishing up 1, 3 and 4 will be a great start. I can then assist with 2 (input streaming), to bring flsamodel in line with the rest of Gensim. |
To get up to speed with Git, I followed the Codecademy Git&Github pro course today. Afterwards, I just tried to fetch and merge the work in your branch. To do so, I used the following: I assumed to see your code when opening This does not work. Which command can I use to pull |
Yeah Probably best to discard any existing mess in your local fork and start fresh: git checkout develop && git fetch upstream && git reset --hard upstream/develop # discard local changes in your develop branch, if any.
git branch -D flsa_fixes # delete your existing local flsa_fixes branch, if any.
git checkout -b my_flsa_fixes # create a new local branch for your changes, named "my_flsa_fixes"
git reset --hard upstream/flsa_fixes # set the content of "my_flsa_fixes" to match the remote "flsa_fixes", to begin with. At that point you should be at commit When your changes are ready for review, open a new pull request (PR) from your Let me know how it goes :) |
Thank you @piskvorky, I will follow your steps! |
Hi guys, I have been checking licensing in some of my projects and I got Are you aware of this? If I'm wrong concerning the licensing, please let me know. Thanks! |
Plus, FuzzyTM is a GPL2/3 license which has a strong copy left requirement. Recently we let poetry update all our dependencies and our corporate scan tool reported a high concern to us with the dependency scan. We would not be able to continue to use Gensim if that library stayed in (I believe this would be the case for most companies/organizations where their IP is in software.) (ahh, I see @victox5 comment on this now as well) |
Gensim itself has a strong copy left license too – LGPL. I'm afraid freeloading corporate concerns are not our primary motivator when choosing dependencies. We offer a commercial (paid) dual licensing for such cases. |
ahh, thanks for the clarification. A mis-understanding on my part with gensims (RaRe-Technologies) position. The company I work for would gladly purchase commercial licensing as needed. |
@damonmerrill that would be great – we welcome contributions on all levels: https://github.com/sponsors/piskvorky |
I note that the license link in the file points at LGPLv3 instead of LGPLv2.1, that should get updated. |
Pylint fixes
My flsa fixes
Yes, I will do this tomorrow! |
See PR #3471 where I apply the required changes to flsa_fixes |
Update the licence link to LGPLv2.1
Fixes #3423. Supersedes #3435, #3436.
This is still work-in-progress and needs finishing up. Namely: