Bug 2307722 - gramps-5.2.3 gives format errors with names
Summary: gramps-5.2.3 gives format errors with names
Keywords:
Status: CLOSED DUPLICATE of bug 2294813
Alias: None
Product: Fedora
Classification: Fedora
Component: python3.13
Version: 41
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Python Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-08-24 16:07 UTC by Steven Usdansky
Modified: 2024-08-24 18:37 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-08-24 18:37:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Steven Usdansky 2024-08-24 16:07:39 UTC
Bug 2294813 describes the problem with gramps.

Recompiled gramps gramps-5.2.3-2.fc41 from source on F41 with the same error.

gramps-5.2.3-1.fc40.noarch.rpm from source on F41 (rather than F40) with the same error.

The error appears to be due to changes in python between python3.12 and python3.13, so filing a bug here

Reproducible: Always

Steps to Reproduce:
1. run gramps
2. load a gramps db
3. select Families from sidebar
Actual Results:  
Several error dialogs appear: 

Gramps has experienced an unexpected error
147835: ERROR: name.py: line 1287: 
Wrong name format string %s %s %s %s
ERROR, Edit Name format in Preferences->Display to correct
Wrong name format string %s %s %s %s
ERROR, Edit Name format in Preferences->Display to correct

Closing those dialogs,
ERROR, Edit Name format in Preferences 
appears for both Father and Mother for all records

Expected Results:  
Names appear as they do in all previous versions of gramps, including when running under F40

This does not appear to corrupt the database; when running under F40, the databases appear to be fine and the program runs as expected.

I have tried the various name formats in the Preferences dialog, and even created a custom format; same error

Comment 1 Ben Beasley 2024-08-24 16:33:35 UTC
Since the regression is reportedly associated with Python 3.13, I set the gramps bug, bug 2294813, to block the PYTHON3.13 tracking bug. However, I don’t see a reason to suspect that there is anything to be fixed in Python 3.13 itself rather than in gramps, so I’m not sure that this bug filed against python3.13 makes sense.

Comment 2 Miro Hrončok 2024-08-24 18:37:00 UTC
This is caused by https://peps.python.org/pep-0558/ and the change is expected.

*** This bug has been marked as a duplicate of bug 2294813 ***


Note You need to log in before you can comment on or make changes to this bug.