oh I know, you're running "python setup.py test".     I'd strongly recommend 
running with the sqla_nose.py runner directly, however this issue is a 
setuptools one, adding this to setup.py will fix:


# Hack to prevent "TypeError: 'NoneType' object is not callable" error
# in multiprocessing/util.py _exit_function when running `python
# setup.py test` (see
# http://www.eby-sarna.com/pipermail/peak/2010-May/003357.html)
try:
    import multiprocessing
except ImportError:
    pass

Seems like this might not be in the current master so this can be added.




On Jul 15, 2013, at 1:08 PM, Michael Bayer <mike...@zzzcomputing.com> wrote:

> im trying to recall if I've seen that one before.   how are tests being run?  
>  this error does not occur in any environment for me.
> 
> 
> On Jul 14, 2013, at 6:18 PM, Hans-Peter Jansen <h...@urpla.net> wrote:
> 
>> On Sonntag, 14. Juli 2013 17:38:12 Michael Bayer wrote:
>>> you can get that right here:
>>> 
>>> www.sqlalchemy.org/changelog/CHANGES_0_7_11
>> 
>> Thanks, great. That fixed all tests, but this  is left still:
>> 
>> [  156s] 
>> ----------------------------------------------------------------------
>> [  156s] Ran 4075 tests in 148.973s
>> [  156s] 
>> [  156s] OK (SKIP=140)
>> [  156s] Error in atexit._run_exitfuncs:
>> [  156s] Traceback (most recent call last):
>> [  156s]   File "/usr/lib64/python2.7/atexit.py", line 24, in _run_exitfuncs
>> [  156s]     func(*targs, **kargs)
>> [  156s]   File "/usr/lib64/python2.7/multiprocessing/util.py", line 284, in 
>> _exit_function
>> [  156s]     info('process shutting down')
>> [  156s] TypeError: 'NoneType' object is not callable
>> [  156s] Error in sys.exitfunc:
>> [  156s] Traceback (most recent call last):
>> [  156s]   File "/usr/lib64/python2.7/atexit.py", line 24, in _run_exitfuncs
>> [  156s]     func(*targs, **kargs)
>> [  156s]   File "/usr/lib64/python2.7/multiprocessing/util.py", line 284, in 
>> _exit_function
>> [  156s]     info('process shutting down')
>> [  156s] TypeError: 'NoneType' object is not callable
>> 
>> Pete
>> 
>> -- 
>> 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/groups/opt_out.
>> 
>> 
> 
> -- 
> 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/groups/opt_out.
> 
> 

-- 
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/groups/opt_out.


Reply via email to