2011/9/20 Robert Kern :
>
> I would additionally suggest that the test-running script also be
> fixed to run correctly under Windows.
Vlad, how you running the tests on windows? Do you experiment the
"infinite dot" issue using nosetests?
Or using the command:
python -c "import sklearn; sklearn.
On Tue, Sep 20, 2011 at 03:17, wrote:
>>But then people will just copy the file and modify it to set n_jobs to
> be greater, and then ask here why it doesn't work on Windows. It's a
> teaching moment. Embrace it!
>
> Yes and no. If I download sklearn on windows and the run make, it doesn't
> fin
>But then people will just copy the file and modify it to set n_jobs to
be greater, and then ask here why it doesn't work on Windows. It's a
teaching moment. Embrace it!
Yes and no. If I download sklearn on windows and the run make, it doesn't
finish the tests. To then tell me that I need to mod
One of the drawcards of using python is that it is relatively platform
independent - so windows users have a reasonable expectation that their code
will run.
Windows itself is not a problem - I've written many C++ programs using
boost::thread that work just fine on windows. Perhaps this require
