Bug#941002: python3-pymca: python3-silx should not be a build dependency

2019-09-23 Thread V . Armando Solé
Package: python3-pymca Version: 5.5.1 Severity: normal Dear Maintainer, Setting python3-silx as a build dependency of python3-pymca prevents building the later on platforms where silx is not available. It would be more convenient to move python3-silx to recommends. The problems solved by moving

Bug#602471: pymca: package unusable

2010-11-15 Thread V. Armando Solé
Hello, From the PyMca side, the problem seems to be solved. By default, PyMca uses the solutions described in previous mail. On linux systems using glibc, the end user or package maintainer, can choose a much cleaner solution based on the use of the strtod_l function. That function is only

Bug#602471: RE : Bug#602471: pymca: package unusable

2010-11-15 Thread V. Armando Solé
Hello, On 15/11/2010 11:20, PICCA Frédéric-Emmanuel wrote: At the end the problem is about the file format used to store the information. SPEC files format which is not LOCAL neutral. By definition, the specfile format is locale C based as it is the format and locale used by SPEC. do

Bug#602471: pymca: package unusable

2010-11-10 Thread V. Armando Solé
Hi On 08/11/2010 18:08, Teemu Ikonen wrote: Hi, Thanks for debugging this. I can reproduce the bug by starting pymca with LANG=de_DE.UTF-8 pymca Interestingly, instantiating QApplication class makes the scanf call in the specfile module use the locale-based numeric format. See the attached