theprojecter / fathom Goto Github PK

For 0.4.0

fathom should provide a class with information about changes that are required 
to move from on database to another database.

Probably running tests could be made much faster, if all operations were done 
as a single transaction. This could be especially true for Sqlite, where there 
are supposed to be possible at most 60 transaction per second in a desktop 
environment. A good solution would be run all creates in setUp as a single 
transaction. If setUp or test itself fails, run all drops a separate 
transactions, because many of them may fail. If both setUp and test itself are 
fine, run drop as a single transaction. If it fails, run all drop operations 
again as separate transactions.

This should be done after 0.3.0 released, so development of 0.4.0 is faster.

[deleted issue]

For example what about get_database_type(username='fathom', password='fathom')? 
More tests are absolutely required for this.

What steps will reproduce the problem?
1. Import the program.
2.
3.

What is the expected output? What do you see instead?
>>> import fathom
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/aklaver/python_virt/3.1/lib/python3.1/site-packages/fathom-0.2.0-py3.1.egg/fathom/__init__.py", line 6, in <module>
    from .utils import get_database_type
  File "/home/aklaver/python_virt/3.1/lib/python3.1/site-packages/fathom-0.2.0-py3.1.egg/fathom/utils.py", line 4, in <module>
    from argparse import ArgumentParser
ImportError: No module named argparse



What version of the product are you using? On what operating system?
Linux Ubuntu 10.04.2 LTS

Please provide any additional information below.
Seems that you need Python 3.2+. This should probably be spelled out more 
clearly.

If someone creates table with name "SoMeTaBlE" fathom should be aware of this 
and perform further selects accordingly. Also utility function for finding 
tables accessed by a function should use this.

0.4.0 :-)