-
Notifications
You must be signed in to change notification settings - Fork 40
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
bimdp autogen breaks with sklearn 0.14.1 #8
Comments
Actually, the whole autogeneration looks fragile wrt unicode characters. |
This actually could be considered a bug in sklearn. There is a recent thread in sklear mailing list about non-ASCII characters in source code: Maybe you could report it on their issue tracker? |
It's not impossible to fix on our side, and it will prevent similar issues in the future. |
If you think you can fix it so that the lib2to3-generated Python3 On Wed 28 Aug, 01:45, Pietro Berkes notifications@github.com wrote:
|
How about we fix it next week? ;-) Niko knows what that code is doing... On Wed, Aug 28, 2013 at 9:48 AM, Tiziano Zito notifications@github.comwrote:
|
Yes, sure, I can work on it next week. I'm also planing to finally take a Cheers, On Wed, Aug 28, 2013 at 11:21 AM, Pietro Berkes notifications@github.comwrote:
|
This is now hitting people (and kicked MDP out of Debian testing: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724146 ). We should really fix it ;) |
Oh, I had completely forgotten about that. I don't remember if we did anything on our side to fix this (but I remember that I did look at the CUDA stuff, so we might have discussed this). |
yes, someone had a fix, maybe Pietro?, but I don't find |
Ok, I can probably work on it next Friday (sorry, I probably won't make it before that). |
You sure it really fixed the problem? With current master I am still getting:
|
Hmm, I can't reproduce it here, maybe it is masked by the other bug? I assume you have scipy installed? |
|
Ops, you are right, I'm confused. I got the error under Python 2 now. I'll do the fix now... |
Fix was pushed in 4fc2b74. |
It is likely caused by a docstring in sklearn containing a unicode character.
The text was updated successfully, but these errors were encountered: