Skip to content
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

Python 3 support ? #3

Open
nSimonFR opened this issue May 3, 2017 · 4 comments
Open

Python 3 support ? #3

nSimonFR opened this issue May 3, 2017 · 4 comments

Comments

@nSimonFR
Copy link

nSimonFR commented May 3, 2017

Do you plan on making this work with Python3 ?
I have started working on a fork on my own, but I am struggling with the Threading module and its usage with TKinter
(I really like the idea though, have been playing with it for a while)

@casparwylie
Copy link
Owner

Great to hear you like it. You can probably tell it's still got some work to go. I'm afraid making it available for python 3 isn't therefore priority. Have you considered just downloading Python 2 for now?

@nSimonFR
Copy link
Author

nSimonFR commented May 3, 2017

I'm currently running it using Python2, but this would be more practical for people that don't want to go through the hassle of installing it ^^
As stated, I started working on Python3 support on my own, it's just really slow because I'm unable to make the threading work, but I might dive onto it later...

@casparwylie
Copy link
Owner

You right, it would be great. Just a matter of time! Many thanks.

@nSimonFR
Copy link
Author

nSimonFR commented May 6, 2017

Well, after trying for some time, it seems hard to make the background training of the network work without a major rewrite for Python3,

This is due to the fact that TKinter does not support multi-threaded operations and threading operations work totally differently in version 3.
I think neural_network_handler.py would have to be rewritten to stop using operations from user_interface_handler.py but instead queue them while the latter treats them by popping them from the queue. (I am no threading expert, but that would be my approach).

In any case, the version I've made still "works", if you consider the fact that you can't stop the training once it's started because everything runs on the same thread ^^
In any case, that is sufficient for what I intend to do with this application !

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

2 participants