TODO for 0.14

[GoogleCodeExporter]

What needs to be done before releasing 0.14?

* Update and check documentation
* Some more fp tests
* Test on some more platforms
* Verify that the new version can be integrated with SymPy and Sage

* ...?

Original issue reported on code.google.com by fredrik....@gmail.com on 22 Jan 2010 at 4:44

[GoogleCodeExporter]

Issue 173 seems critical, but I can't fix it since I'm unable to reproduce the 
error,
at least not until I get an Ubuntu system up and running again.

Original comment by fredrik....@gmail.com on 22 Jan 2010 at 4:45

[GoogleCodeExporter]

I think issue 173 is not critical, as we do not rely on py.test.

Original comment by Vinzent.Steinberg@gmail.com on 24 Jan 2010 at 12:05

[GoogleCodeExporter]

Also, for Sage integration: http://trac.sagemath.org/sage_trac/ticket/8159

Original comment by fredrik....@gmail.com on 3 Feb 2010 at 1:48

[GoogleCodeExporter]

I updated the documentation. I think I'm happy now.

So mostly a bit more testing.

Original comment by fredrik....@gmail.com on 4 Feb 2010 at 1:54

[GoogleCodeExporter]

I think there's a mixture of Windows/Unix line endings currently... this 
definitely
should be fixed.

Original comment by fredrik....@gmail.com on 4 Feb 2010 at 2:11

[GoogleCodeExporter]

Yeah. What do you want? We could use sympy's script to convert everything to 
Unix
endings. Or modify it to convert to Windows endings.

Original comment by Vinzent.Steinberg@gmail.com on 4 Feb 2010 at 12:20

[GoogleCodeExporter]

I converted all .py files in the main directory to Windows, since it's what most
lines were already. I'm not entirely opposed to changing everything to Unix 
instead,
but let's wait with that.

Original comment by fredrik....@gmail.com on 4 Feb 2010 at 2:45

[GoogleCodeExporter]

Original comment by Vinzent.Steinberg@gmail.com on 9 Feb 2010 at 11:57

• Changed state: Fixed