Bug 2120805

Summary:	Use f-strings in tuna where possible
Product:	Red Hat Enterprise Linux 8	Reporter:	John Kacur <jkacur>
Component:	tuna	Assignee:	Leah Leshchinsky <lleshchi>
Status:	CLOSED ERRATA	QA Contact:	Qiao Zhao <qzhao>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.8	CC:	bhu, qzhao, rt-maint
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.8
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tuna-0.18-4.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-16 09:03:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description John Kacur 2022-08-23 18:34:13 UTC

This bug was initially created as a copy of Bug #2120803

I am copying this bug because: 

We need to do this in rhel-8.8 too


Description of problem:

f-strings increase the readability and reduce the code size.

tuna has quite a lot of places where f-strings could be used, so let's change this where possible.

Note: No functional change

Note: The changes here are in the getopt branch

Comment 7 errata-xmlrpc 2023-05-16 09:03:40 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (tuna bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2964