picca

to reproduce the problem here the code, I am using ``` import sys import numpy from pyFAI.calibration import calib, get_detector from pyFAI.calibrant import ALL_CALIBRANTS def get_calibrant(calibrant_name): return ALL_CALIBRANTS[calibrant_name] def calibration(img,...

Just for information, I obtained the same issue using directly the pyFAI-calib command line of the debian package root@diffabs6:/home/experiences/instrumentation/picca/Debian/sida/sida# rmadison pyfai debian: pyfai | 0.3.5-1 | wheezy | source, amd64,...

In fact the error is not the same Modify parameters (or ? for help)? done Traceback (most recent call last): File "/usr/bin/pyFAI-calib", line 59, in c.gui_peakPicker() File "/usr/lib/python2.7/dist-packages/pyFAI/calibration.py", line 1480,...

In Debian I can not downgrad fabio :((. Is it possible to release a new pyFAI with the fix ? if not can you point me to the right commit...

I fount this 432853480896a32408fdbb3ba9a660279b6e0b92 right ?

Here the backtrace ``` Program received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 ../sysdeps/unix/sysv/linux/raise.c: Aucun fichier ou dossier de ce type. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1...

This is strange it seems to be openssl related.

I build the doc with all version of the python available, it allows to catch more errors during the build, process. Beware python-dbg is not an equivalent of -dbgsym auto-generated...

In that case can you add a tag showing that this is trivial. then I will ask my apprentice to look after these trivial changes. thanks Fred

Here a bunch of warning due to unclosed files ``` INFO:pyFAI.setup:Build man for entry-point target 'check_calib' /builds/science-team/pyfai/debian/output/source_dir/setup.py:349: ResourceWarning: unclosed file synopsis = self.get_synopsis(module_name, env) ResourceWarning: Enable tracemalloc to get the...