[sqlalchemy] Re: same code same database but the not same insert result

2014-07-09 Thread 'Frank Liou' via sqlalchemy 

>
> but i mean
>

i encoded 12345678  that should be   MTIzNDU2Nzg but \
x4d54497a4e4455324e7a673d

the same code 

why get not the same result?

-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.

Re: [sqlalchemy] unit tests failing on 0.9.6

2014-07-09 Thread Jason Newton 
Works for me with doing py.test, I can live with it.


On Wed, Jul 9, 2014 at 1:55 PM, Mike Bayer  wrote:

>  OK this is fixed now, I hope.
>
>
>
> On 7/9/14, 9:52 AM, Mike Bayer wrote:
>
> OK what if you just run it via "py.test" ?the distutils/setuptools
> approach is so often problematic.
>
> issue appeared in 0.9.6, not 0.9.5 ?
>
>
>
>
> On 7/9/14, 3:01 AM, Jason Newton wrote:
>
> Yes, it seems to me like it gets to the end and then commits suicide just
> before returning, but I wasn't able to make heads or tails.
>
> Nothing fancy to running it - just unpack the pypi archive, and run python
> setup.py test.  I first ran into it when updating the opensuse package from
> 0.8.5 but it's reproducable inside the chroot jail OBS creates as well as
> on my desktop.
>
> On Tuesday, July 8, 2014 3:43:02 PM UTC-7, Michael Bayer wrote:
>>
>>  how are you running them?
>>
>> it isn't reporting any "failure", this seems like it's finding a bad test
>> case.   do you have any test.py type stuff it might be hitting?
>>
>>
>>
>> On 7/8/14, 5:56 PM, Jason Newton wrote:
>>
>> Any thoughts on why the unit testing is failing?
>>
>> platform linux2 -- Python 2.7.6 -- py-1.4.20 -- pytest-2.5.2 --
>> /usr/bin/python
>>
>> 
>>
>> == 5776 passed,
>> 688 skipped in 139.77 seconds ==
>> =
>> Traceback (most recent call last):
>>   File "setup.py", line 165, in 
>> run_setup(True)
>>   File "setup.py", line 146, in run_setup
>> **kwargs
>>   File "/usr/lib64/python2.7/distutils/core.py", line 152, in setup
>> dist.run_commands()
>>   File "/usr/lib64/python2.7/distutils/dist.py", line 953, in
>> run_commands
>> self.run_command(cmd)
>>   File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command
>> cmd_obj.run()
>>   File "/usr/lib/python2.7/site-packages/setuptools/command/test.py",
>> line 146, in run
>> self.with_project_on_sys_path(self.run_tests)
>>   File "/usr/lib/python2.7/site-packages/setuptools/command/test.py",
>> line 127, in with_project_on_sys_path
>> func()
>>   File "/usr/lib/python2.7/site-packages/setuptools/command/test.py",
>> line 167, in run_tests
>> testRunner=self._resolve_as_ep(self.test_runner),
>>   File "/usr/lib64/python2.7/unittest/main.py", line 94, in __init__
>> self.parseArgs(argv)
>>   File "/usr/lib64/python2.7/unittest/main.py", line 149, in parseArgs
>> self.createTests()
>>   File "/usr/lib64/python2.7/unittest/main.py", line 158, in createTests
>> self.module)
>>   File "/usr/lib64/python2.7/unittest/loader.py", line 130, in
>> loadTestsFromNames
>> suites = [self.loadTestsFromName(name, module) for name in names]
>>   File "/usr/lib64/python2.7/unittest/loader.py", line 122, in
>> loadTestsFromName
>> (obj, test))
>> TypeError: calling  returned 0, not a test
>>
>>
>>  -Jason
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "sqlalchemy" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sqlalchemy+...@googlegroups.com.
>> To post to this group, send email to sqlal...@googlegroups.com.
>> Visit this group at http://groups.google.com/group/sqlalchemy.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>   --
> You received this message because you are subscribed to the Google Groups
> "sqlalchemy" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sqlalchemy+unsubscr...@googlegroups.com.
> To post to this group, send email to sqlalchemy@googlegroups.com.
> Visit this group at http://groups.google.com/group/sqlalchemy.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sqlalchemy" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sqlalchemy+unsubscr...@googlegroups.com.
> To post to this group, send email to sqlalchemy@googlegroups.com.
> Visit this group at http://groups.google.com/group/sqlalchemy.
> For more options, visit https://groups.google.com/d/optout.
>
>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "sqlalchemy" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sqlalchemy/-An7vTSq6xo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sqlalchemy+unsubscr...@googlegroups.com.
> To post to this group, send email to sqlalchemy@googlegroups.com.
> Visit this group at http://groups.google.com/group/sqlalchemy.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to thi

Re: [sqlalchemy] problems with mysql reflect

2014-07-09 Thread Paul Molodowitch 
Sure - I think it's the same as the original poster's, but the traceback
I'm getting is:

>>> inspect(Project).relationships
Traceback (most recent call last):
  File "", line 1, in 
  File "./sqlalchemy/util/langhelpers.py", line 712, in __get__
obj.__dict__[self.__name__] = result = self.fget(obj)
  File "./sqlalchemy/orm/mapper.py", line 2037, in relationships
return self._filter_properties(properties.RelationshipProperty)
  File "./sqlalchemy/orm/mapper.py", line 2054, in _filter_properties
configure_mappers()
  File "./sqlalchemy/orm/mapper.py", line 2560, in configure_mappers
mapper._post_configure_properties()
  File "./sqlalchemy/orm/mapper.py", line 1673, in
_post_configure_properties
prop.init()
  File "./sqlalchemy/orm/interfaces.py", line 143, in init
self.do_init()
  File "./sqlalchemy/orm/relationships.py", line 1510, in do_init
self._setup_join_conditions()
  File "./sqlalchemy/orm/relationships.py", line 1586, in
_setup_join_conditions
can_be_synced_fn=self._columns_are_mapped
  File "./sqlalchemy/orm/relationships.py", line 1849, in __init__
self._determine_joins()
  File "./sqlalchemy/orm/relationships.py", line 1915, in _determine_joins
consider_as_foreign_keys=consider_as_foreign_keys
  File "", line 2, in join_condition
  File "./sqlalchemy/sql/selectable.py", line 692, in _join_condition
b.foreign_keys,
AttributeError: 'tuple' object has no attribute 'foreign_keys'



On Wed, Jul 9, 2014 at 2:04 PM, Mike Bayer  wrote:

>
> On 7/9/14, 3:41 PM, Paul Molodowitch wrote:
>
> I just ran into the same problem, using python 2.6 + sqlalchemy 0.9.4 /
> 0.9.6 + MySQL.
>
>  The problem in my case IS definitely related to python 2.6 - basically,
> python 2.6 doesn't allow unicode keywords, while 2.7 does. Ie, if you do
> this:
>
>   def foo(**kwargs):
>   print kwargs
>  foo(**{u'thing':1})
>
>
>  ...it will work in 2.7, but give this error in 2.6:
>
>  TypeError: foo() keywords must be strings
>
>
>  For reference, these were the table.dialect_kwargs.keys() that were
> making trouble in 2.6:
>
>  [u'mysql_comment', u'mysql_engine', u'mysql_default charset']
>
>
>  Fine, except for the fact that they're unicode...
>
> OK but this is not a codepath within SQLAlchemy's MySQL reflection code.
> I'm PDBing right now into 0.9, using py2.6 + use_unicode=1; the reflected
> table options are sent directly into table.kwargs, not using the
> constructor or any **kw system.  the tests pass, and the keys are coming
> back as u''.
>
> if you can show me where table.kwargs gets used implicitly as a
> constructor arg i can fix that.
>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "sqlalchemy" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sqlalchemy/E3MhX1m8QqQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sqlalchemy+unsubscr...@googlegroups.com.
> To post to this group, send email to sqlalchemy@googlegroups.com.
> Visit this group at http://groups.google.com/group/sqlalchemy.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.

Re: [sqlalchemy] problems with mysql reflect

2014-07-09 Thread Mike Bayer 

On 7/9/14, 3:41 PM, Paul Molodowitch wrote:
> I just ran into the same problem, using python 2.6 + sqlalchemy 0.9.4
> / 0.9.6 + MySQL.
>
> The problem in my case IS definitely related to python 2.6 -
> basically, python 2.6 doesn't allow unicode keywords, while 2.7 does.
> Ie, if you do this:
>
> def foo(**kwargs):
> print kwargs
> foo(**{u'thing':1})
>
>
> ...it will work in 2.7, but give this error in 2.6:
>
> TypeError: foo() keywords must be strings
>
>
> For reference, these were the table.dialect_kwargs.keys() that were
> making trouble in 2.6:
>
> [u'mysql_comment', u'mysql_engine', u'mysql_default charset']
>
>
> Fine, except for the fact that they're unicode...
OK but this is not a codepath within SQLAlchemy's MySQL reflection
code.   I'm PDBing right now into 0.9, using py2.6 + use_unicode=1; the
reflected table options are sent directly into table.kwargs, not using
the constructor or any **kw system.  the tests pass, and the keys are
coming back as u''.

if you can show me where table.kwargs gets used implicitly as a
constructor arg i can fix that.

-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.

Re: [sqlalchemy] unit tests failing on 0.9.6

2014-07-09 Thread Mike Bayer 
OK this is fixed now, I hope.


On 7/9/14, 9:52 AM, Mike Bayer wrote:
> OK what if you just run it via "py.test" ?the distutils/setuptools
> approach is so often problematic.
>
> issue appeared in 0.9.6, not 0.9.5 ?
>
>
>
>
> On 7/9/14, 3:01 AM, Jason Newton wrote:
>> Yes, it seems to me like it gets to the end and then commits suicide
>> just before returning, but I wasn't able to make heads or tails.
>>
>> Nothing fancy to running it - just unpack the pypi archive, and run
>> python setup.py test.  I first ran into it when updating the opensuse
>> package from 0.8.5 but it's reproducable inside the chroot jail OBS
>> creates as well as on my desktop.
>>
>> On Tuesday, July 8, 2014 3:43:02 PM UTC-7, Michael Bayer wrote:
>>
>> how are you running them?
>>
>> it isn't reporting any "failure", this seems like it's finding a
>> bad test case.   do you have any test.py type stuff it might be
>> hitting?
>>
>>
>>
>> On 7/8/14, 5:56 PM, Jason Newton wrote:
>>> Any thoughts on why the unit testing is failing?
>>>
>>> platform linux2 -- Python 2.7.6 -- py-1.4.20 -- pytest-2.5.2 --
>>> /usr/bin/python
>>>
>>> 
>>>
>>> == 5776
>>> passed, 688 skipped in 139.77 seconds
>>> ===
>>> Traceback (most recent call last):
>>>   File "setup.py", line 165, in 
>>> run_setup(True)
>>>   File "setup.py", line 146, in run_setup
>>> **kwargs
>>>   File "/usr/lib64/python2.7/distutils/core.py", line 152, in setup
>>> dist.run_commands()
>>>   File "/usr/lib64/python2.7/distutils/dist.py", line 953, in
>>> run_commands
>>> self.run_command(cmd)
>>>   File "/usr/lib64/python2.7/distutils/dist.py", line 972, in
>>> run_command
>>> cmd_obj.run()
>>>   File
>>> "/usr/lib/python2.7/site-packages/setuptools/command/test.py",
>>> line 146, in run
>>> self.with_project_on_sys_path(self.run_tests)
>>>   File
>>> "/usr/lib/python2.7/site-packages/setuptools/command/test.py",
>>> line 127, in with_project_on_sys_path
>>> func()
>>>   File
>>> "/usr/lib/python2.7/site-packages/setuptools/command/test.py",
>>> line 167, in run_tests
>>> testRunner=self._resolve_as_ep(self.test_runner),
>>>   File "/usr/lib64/python2.7/unittest/main.py", line 94, in __init__
>>> self.parseArgs(argv)
>>>   File "/usr/lib64/python2.7/unittest/main.py", line 149, in
>>> parseArgs
>>> self.createTests()
>>>   File "/usr/lib64/python2.7/unittest/main.py", line 158, in
>>> createTests
>>> self.module)
>>>   File "/usr/lib64/python2.7/unittest/loader.py", line 130, in
>>> loadTestsFromNames
>>> suites = [self.loadTestsFromName(name, module) for name in
>>> names]
>>>   File "/usr/lib64/python2.7/unittest/loader.py", line 122, in
>>> loadTestsFromName
>>> (obj, test))
>>> TypeError: calling  returned 0, not
>>> a test
>>>
>>>
>>> -Jason
>>> -- 
>>> You received this message because you are subscribed to the
>>> Google Groups "sqlalchemy" group.
>>> To unsubscribe from this group and stop receiving emails from
>>> it, send an email to sqlalchemy+...@googlegroups.com .
>>> To post to this group, send email to sqlal...@googlegroups.com
>>> .
>>> Visit this group at http://groups.google.com/group/sqlalchemy
>>> .
>>> For more options, visit https://groups.google.com/d/optout
>>> .
>>
>> -- 
>> You received this message because you are subscribed to the Google
>> Groups "sqlalchemy" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to sqlalchemy+unsubscr...@googlegroups.com
>> .
>> To post to this group, send email to sqlalchemy@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/sqlalchemy.
>> For more options, visit https://groups.google.com/d/optout.
>
> -- 
> You received this message because you are subscribed to the Google
> Groups "sqlalchemy" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to sqlalchemy+unsubscr...@googlegroups.com
> .
> To post to this group, send email to sqlalchemy@googlegroups.com
> .
> Visit this group at http://groups.google.com/group/sqlalchemy.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sq

Re: [sqlalchemy] problems with mysql reflect

2014-07-09 Thread Paul Molodowitch 
I just ran into the same problem, using python 2.6 + sqlalchemy 0.9.4 / 
0.9.6 + MySQL.

The problem in my case IS definitely related to python 2.6 - basically, 
python 2.6 doesn't allow unicode keywords, while 2.7 does. Ie, if you do 
this:

def foo(**kwargs):
print kwargs
foo(**{u'thing':1})


...it will work in 2.7, but give this error in 2.6:

TypeError: foo() keywords must be strings


For reference, these were the table.dialect_kwargs.keys() that were making 
trouble in 2.6:

[u'mysql_comment', u'mysql_engine', u'mysql_default charset']


Fine, except for the fact that they're unicode...

-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.

[sqlalchemy] Re: same code same database but the not same insert result

2014-07-09 Thread Jonathan Vanasco 
Postgres can handle UTF-8 encoded data.   you would probably be better off 
not encoding stuff into b64 in python and just using postgres to store the 
utf8 data.

The string "12345678" is not base64 encoded.  That was probably an entry 
inserted from another bit of code.

>>> print base64.b64encode("12345678")
MTIzNDU2Nzg=

These strings can't be base64 decoded :
>>> print base64.b64decode("\x4d54497a4e4455324e7a673d")
>>> print base64.b64decode("x4d54497a4e4455324e7a673d")

This one can :
>>> print base64.b64decode("4d54497a4e4455324e7a673d")


-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.

Re: [sqlalchemy] unit tests failing on 0.9.6

2014-07-09 Thread Mike Bayer 
OK what if you just run it via "py.test" ?the distutils/setuptools
approach is so often problematic.

issue appeared in 0.9.6, not 0.9.5 ?




On 7/9/14, 3:01 AM, Jason Newton wrote:
> Yes, it seems to me like it gets to the end and then commits suicide
> just before returning, but I wasn't able to make heads or tails.
>
> Nothing fancy to running it - just unpack the pypi archive, and run
> python setup.py test.  I first ran into it when updating the opensuse
> package from 0.8.5 but it's reproducable inside the chroot jail OBS
> creates as well as on my desktop.
>
> On Tuesday, July 8, 2014 3:43:02 PM UTC-7, Michael Bayer wrote:
>
> how are you running them?
>
> it isn't reporting any "failure", this seems like it's finding a
> bad test case.   do you have any test.py type stuff it might be
> hitting?
>
>
>
> On 7/8/14, 5:56 PM, Jason Newton wrote:
>> Any thoughts on why the unit testing is failing?
>>
>> platform linux2 -- Python 2.7.6 -- py-1.4.20 -- pytest-2.5.2 --
>> /usr/bin/python
>>
>> 
>>
>> == 5776
>> passed, 688 skipped in 139.77 seconds
>> ===
>> Traceback (most recent call last):
>>   File "setup.py", line 165, in 
>> run_setup(True)
>>   File "setup.py", line 146, in run_setup
>> **kwargs
>>   File "/usr/lib64/python2.7/distutils/core.py", line 152, in setup
>> dist.run_commands()
>>   File "/usr/lib64/python2.7/distutils/dist.py", line 953, in
>> run_commands
>> self.run_command(cmd)
>>   File "/usr/lib64/python2.7/distutils/dist.py", line 972, in
>> run_command
>> cmd_obj.run()
>>   File
>> "/usr/lib/python2.7/site-packages/setuptools/command/test.py",
>> line 146, in run
>> self.with_project_on_sys_path(self.run_tests)
>>   File
>> "/usr/lib/python2.7/site-packages/setuptools/command/test.py",
>> line 127, in with_project_on_sys_path
>> func()
>>   File
>> "/usr/lib/python2.7/site-packages/setuptools/command/test.py",
>> line 167, in run_tests
>> testRunner=self._resolve_as_ep(self.test_runner),
>>   File "/usr/lib64/python2.7/unittest/main.py", line 94, in __init__
>> self.parseArgs(argv)
>>   File "/usr/lib64/python2.7/unittest/main.py", line 149, in
>> parseArgs
>> self.createTests()
>>   File "/usr/lib64/python2.7/unittest/main.py", line 158, in
>> createTests
>> self.module)
>>   File "/usr/lib64/python2.7/unittest/loader.py", line 130, in
>> loadTestsFromNames
>> suites = [self.loadTestsFromName(name, module) for name in names]
>>   File "/usr/lib64/python2.7/unittest/loader.py", line 122, in
>> loadTestsFromName
>> (obj, test))
>> TypeError: calling  returned 0, not a
>> test
>>
>>
>> -Jason
>> -- 
>> You received this message because you are subscribed to the
>> Google Groups "sqlalchemy" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to sqlalchemy+...@googlegroups.com .
>> To post to this group, send email to sqlal...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/sqlalchemy
>> .
>> For more options, visit https://groups.google.com/d/optout
>> .
>
> -- 
> You received this message because you are subscribed to the Google
> Groups "sqlalchemy" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to sqlalchemy+unsubscr...@googlegroups.com
> .
> To post to this group, send email to sqlalchemy@googlegroups.com
> .
> Visit this group at http://groups.google.com/group/sqlalchemy.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.

Re: [sqlalchemy] unit tests failing on 0.9.6

2014-07-09 Thread Jason Newton 
Yes, it seems to me like it gets to the end and then commits suicide just 
before returning, but I wasn't able to make heads or tails.

Nothing fancy to running it - just unpack the pypi archive, and run python 
setup.py test.  I first ran into it when updating the opensuse package from 
0.8.5 but it's reproducable inside the chroot jail OBS creates as well as 
on my desktop.

On Tuesday, July 8, 2014 3:43:02 PM UTC-7, Michael Bayer wrote:
>
>  how are you running them?
>
> it isn't reporting any "failure", this seems like it's finding a bad test 
> case.   do you have any test.py type stuff it might be hitting?
>
>
>
> On 7/8/14, 5:56 PM, Jason Newton wrote:
>  
> Any thoughts on why the unit testing is failing?
>
> platform linux2 -- Python 2.7.6 -- py-1.4.20 -- pytest-2.5.2 -- 
> /usr/bin/python
>
> 
>
> == 5776 passed, 
> 688 skipped in 139.77 seconds 
> ===
> Traceback (most recent call last):
>   File "setup.py", line 165, in 
> run_setup(True)
>   File "setup.py", line 146, in run_setup
> **kwargs
>   File "/usr/lib64/python2.7/distutils/core.py", line 152, in setup
> dist.run_commands()
>   File "/usr/lib64/python2.7/distutils/dist.py", line 953, in run_commands
> self.run_command(cmd)
>   File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command
> cmd_obj.run()
>   File "/usr/lib/python2.7/site-packages/setuptools/command/test.py", line 
> 146, in run
> self.with_project_on_sys_path(self.run_tests)
>   File "/usr/lib/python2.7/site-packages/setuptools/command/test.py", line 
> 127, in with_project_on_sys_path
> func()
>   File "/usr/lib/python2.7/site-packages/setuptools/command/test.py", line 
> 167, in run_tests
> testRunner=self._resolve_as_ep(self.test_runner),
>   File "/usr/lib64/python2.7/unittest/main.py", line 94, in __init__
> self.parseArgs(argv)
>   File "/usr/lib64/python2.7/unittest/main.py", line 149, in parseArgs
> self.createTests()
>   File "/usr/lib64/python2.7/unittest/main.py", line 158, in createTests
> self.module)
>   File "/usr/lib64/python2.7/unittest/loader.py", line 130, in 
> loadTestsFromNames
> suites = [self.loadTestsFromName(name, module) for name in names]
>   File "/usr/lib64/python2.7/unittest/loader.py", line 122, in 
> loadTestsFromName
> (obj, test))
> TypeError: calling  returned 0, not a test
>
>
>  -Jason
>  -- 
> You received this message because you are subscribed to the Google Groups 
> "sqlalchemy" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sqlalchemy+...@googlegroups.com .
> To post to this group, send email to sqlal...@googlegroups.com 
> .
> Visit this group at http://groups.google.com/group/sqlalchemy.
> For more options, visit https://groups.google.com/d/optout.
>
>
>  

-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.