Ivan K added the comment:
This behaviour was reproduced on Ubuntu 12.04 and on Centos 7 (centos image
running on vagrant) so I don't expect this is ddistro specific
--
___
Python tracker
<http://bugs.python.org/is
Ivan K added the comment:
Sorry, forget to answer.
I think I know the reason.
Issue I think placed inside ATLAS library.
Issue not reproducable on Mac OS X because it's have a bit different thread
model.
The only single platform is Linux (not tested on Windows btw). So main guess
righ
Ivan K added the comment:
Yes, it work fine and output was
LogisticRegression(C=1.0, class_weight=None, dual=False, fit_intercept=True,
intercept_scaling=1, penalty=l2, random_state=None, tol=0.0001)
--
___
Python tracker
<h
Ivan K added the comment:
Sorry, stupdi question. Forget that this is from my gist
--
___
Python tracker
<http://bugs.python.org/issue21162>
___
___
Python-bug
Ivan K added the comment:
Sorry, could you specify what is 'func' ?
--
___
Python tracker
<http://bugs.python.org/issue21162>
___
___
Python-bugs-l
Ivan K added the comment:
Yes, I'm not using any tool. Code just not working.
--
___
Python tracker
<http://bugs.python.org/issue21162>
___
___
Python-bugs-l
Ivan K added the comment:
Sorry, I'm not sure I describe it correct. Freeze that means = goes fozen, so
stop progress. It's do no do anything, but computations still load single core
of my cpu for 100% untill I do not kill the python process.
But the same code work's fine if e
New submission from Ivan K:
Here is a code. https://gist.github.com/anonymous/9994217 When I run it in
freeze and never end. If I run it without pool with loop or joblib - it works
fine.
Also there is a question on stackoverflow:
http://stackoverflow.com/q/22881850/1888017
Python 2.7.6
