#4075 scikits.statmodels 0.3.1


Does this package have OS version restrictions? py25 only on OS X 10.5,106; py26 and py 27 also on 10.7
Which section does it belong in? libs/pythonmody
Have you built it with -m --build-as-nobody? yes validated ok


  • It depends on scipy-py, but there's no scipy-py25, so I removed the py25 variant. There's also no matplotlib-py26 on 10.7, so I modified the Distribution field to instead to limit py26 to 10.5/10.6.

    I manually ran "%p/bin/python2.7 setup.py test" inside the build dir and got the following error:

    OK (skipped=15)
    Error in atexit._run_exitfuncs:
    Traceback (most recent call last):
    File "/sw/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
    File "/sw/lib/python2.7/multiprocessing/util.py", line 284, in _exit_function
    info('process shutting down')
    TypeError: 'NoneType' object is not callable
    Error in sys.exitfunc:
    Traceback (most recent call last):
    File "/sw/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
    File "/sw/lib/python2.7/multiprocessing/util.py", line 284, in _exit_function
    info('process shutting down')
    TypeError: 'NoneType' object is not callable

    I have no idea if that's fixable, or if it's expected brokenness. It's always good to try and run tests (via InfoTest). In cases of known brokenness, if the test can be disabled, then it at least helps sanity check that nothing went wrong with building the package.

    statsmodels-py did finish building, so it's just a matter of clarifying the tests issue. If you want py25 and py26 available again, please contact the maintainers of scipy-py and matplotlib-py about adding variants to their packages.

    • milestone: 373615 --> Awaiting_Update_from_Submitter
  • Hello,

    Any word on what to do about the Tests issue? If the tests can't be fixed, then that should be noted, and the package committed as is.

  • Currently working on it.

  • What is the status of this item?

  • Current version has patsy as dependency (not available in Fink). Have to create pasty-py first.

  • Have created patsy-py will submit separately. If accepted I will submit info file for stat models

  • Here comes statsmodels-py27 v. 0.5.0
    when doing 'fink -m rebuild' it returns 3 failures, two seems to be a known issue from what I see in the respective git repository. updated and rebuilt all dependencies - please advise.
    should go to sci
    new package

  • Interestingly, I get 9 failures due to the same thing:

    ERROR: Failure: RuntimeError (could not create GdkCursor object)
    Traceback (most recent call last):
      File "/sw/lib/python2.7/site-packages/nose/loader.py", line 413, in loadTestsFromName
        addr.filename, addr.module)
      File "/sw/lib/python2.7/site-packages/nose/importer.py", line 47, in importFromPath
        return self.importFromDir(dir_path, fqname)
      File "/sw/lib/python2.7/site-packages/nose/importer.py", line 94, in importFromDir
        mod = load_module(part_fqname, fh, filename, desc)
      File "/sw/build.build/statsmodels-py27-0.5.0-1/statsmodels-0.5.0/statsmodels/stats/tests/test_power.py", line 28, in <module>
        import matplotlib.pyplot as plt  #makes plt available for test functions
      File "/sw/lib/python2.7/site-packages/matplotlib/pyplot.py", line 98, in <module>
        _backend_mod, new_figure_manager, draw_if_interactive, _show = pylab_setup()
      File "/sw/lib/python2.7/site-packages/matplotlib/backends/__init__.py", line 28, in pylab_setup
      File "/sw/lib/python2.7/site-packages/matplotlib/backends/backend_gtkagg.py", line 10, in <module>
        from matplotlib.backends.backend_gtk import gtk, FigureManagerGTK, FigureCanvasGTK,\
      File "/sw/lib/python2.7/site-packages/matplotlib/backends/backend_gtk.py", line 58, in <module>
        cursors.MOVE          : gdk.Cursor(gdk.FLEUR),
    RuntimeError: could not create GdkCursor object

    However, those were easily fixed by running the tests inside xvfb-run so that the fink-bld user had access to the X display. When I did that, all tests passed.

    Ran 2857 tests in 498.527s
    OK (skipped=19)

    Which tests failed for you (and on what OS X version)?

    If a tests is known to fail, common solutions are to 1) deactivate it, 2) find and apply the upstream patch, or 3) turn the test into an XFAIL (not always possible).