sfe/base/ioutils.py sucks, as it is probably the oldest part of the code. it will contain only the low-level reading/writing functions, all the other belong to meshio.py. I just have not moved the code yet, because I wanted to see your code and its implications first. And I was lazy. :)
My implemenation is ugly. It does the job though.
My idea is to have one .py file for each format (for example in sfe/fem/io dir?) that implements everything there is to this format - reading mesh, writing mesh, writing a solution, so that it's not scattered all over sfepy. Do you agree? Are there any pitfalls regarding the sfe/base/ioutils.py file?
Well, it depends on how many and how big those read/write classes are going to be. I can bear having 3-4 in one file, but it will probably grow beyond that... So let's do the split, but let me first think about
how to deal with the high-level writing functions from ioutils.py. I will move them (probably) to meshio.py classes, and then we may split the file.
Cool. So should I wait with the refactoring? I'll be working on this today and over the weekend. So if you won't be around, I'll try to do it as best as I can and send you a patch, so that on Monday you can review it/apply it. BTW, I won't be available on Monday through Thursday next week.