Bug #3866: Errors creating objects cannot be displayed - Lasso - Redmine Entr’ouvert

Bug #3866

Errors creating objects cannot be displayed

Ajouté par Frédéric Péters il y a plus de 10 ans. Mis à jour il y a plus de 10 ans.

Statut:

Fermé

Priorité:

Normal

Assigné à:

Catégorie:

Version cible:

Début:

23 octobre 2013

Echéance:

% réalisé:

100%

Temps estimé:

Patch proposed:

Planning:

Description

The binding does a raise Error('failed to create object') but the local Error exception class expects a lasso error code, and will thus fail if printed.

  File ".../lasso.py", line 54, in __str__
    return '<lasso.%s(%s): %s>' % (self.__class__.__name__, self.code,
             _lasso.strError(self.code))
  TypeError: an integer is required

Fichiers

0001-python-do-not-fail-displaying-a-non-C-error-fixes-38.patch (1,34 ko) 0001-python-do-not-fail-displaying-a-non-C-error-fixes-38.patch

Frédéric Péters, 23 octobre 2013 15:35

Révisions associées

Révision 08054853 (diff)
Ajouté par Frédéric Péters il y a plus de 10 ans

python: do not fail displaying a non-C error (fixes #3866)

The binding does a raise Error('failed to create object') but the local Error
exception class expects a lasso error code, and will thus fail if printed.

File ".../lasso.py", line 54, in str
    return '&lt;lasso.%s(%s): %s&gt;' % (self.__class__.__name__, self.code,
             _lasso.strError(self.code))
  TypeError: an integer is required