Fix Windows tests about nbstripout HOT 5 CLOSED

@arobrien interested to help with this?

from nbstripout.

I've tried to use cram myself for a project and got bitten by this.

This commit zertrin@920bb05 tries to minimize the problem but doesn't solve it... Lines with options like (re) can't be fixed by the core.autocrlf trick.

My conclusion at this point is that cram is not usable on windows. I have dropped it from my project since a look at their issue tracker and git activity shows that the project is not gonna fix this anytime soon.

from nbstripout.

@zertrin thanks for looking into this. Great idea using core.autocrlf, I'll apply that change anyway, even though it doesn't fix it.

The only solution at this point is probably forking cram until @Brodie picks up the project again.

from nbstripout.

https://github.com/brodie/cram hasn't had a release since 2016 and is now archived. It's probably easier to port the tests to another framework than to fix/update/fork/whatever cram.

from nbstripout.

Yes, that's what I'm intending to do. See #165.

from nbstripout.