Using f-string with format depending on a condition

Question

How can I use f-string with logic to format an int as a float? I would like if ppl is True to format num to 2 decimal places, and if ppl is False to rformat it as whatever it is.

Something like string = f'i am {num:.2f if ppl else num}' but this does not work. The below code demonstrates the behaviour that I want to achieve with a simpler f-string if possible:

ppl = True
num = 3
string = f'I am {num:.2f}' if ppl else f'I am {num}'
print(string)
#if ppl False
#=> i am 3
#if ppl True
#=> i am 3.00

Answer 1

I would recommend that you actually separate the fstring into two lines

num_str = f'{num:.2f}' if ppl else f'{num}'
final_str = f'I am {num_str}'

That way each line is as simple as it can be.

Answer 2

There's a lot to unravel in your question, but I'll give it a shot. At a high-level it sounds like you're looking for a multi-tenant system.

and pretty much everything you're saying is on point, you probably just need an example to get going. If so, check out Microsoft's example of a multi-tenant system. It might be enough to get you going.

There's several different approaches to a multi-tenant system depending on your business requirements, but here's a few of the more common approaches I've seen used:

1. Database Isolation - Each Company would be in a separate database. When a user from Company A connected, you would be able to look up which database/schema you should connect too.
2. Row Level - All companies store data in the same tables, but there's a column called something like "company_id". Every time you query against the table, you filter on company_id based on which user is logged in.
3. Instance per tenant (AKA Standalone) - On this approach you essentially have multiple web servers running, one per company. They are completely isolated from the web server all the way down to the database. This can be desirable in some situations, but requires a bit more hardware. On the code side, you can handle this fairly effectively with just moving relevant settings into the appsettings file.

Further Reading:

• Identity Management In Multitenant Applications
• Multi-Tenant Patterns on SQL Databases
• Row Level Multi-Tenant Example

The implementation for the different companies changes depending on how you decide to implement the multi-tenant system. So it's hard for me to give you any concrete advice on implementation.

The only word of warning I'd give is think through the relationship between a user and a company. That could change/complicate your implementation fairly quickly.

Can a user be part of Company A and Company B at the same time?

Hope this helps a bit, and best of luck.