We must not forget that the FakerLibrary is used by a group of users in productive test cases or tasks.
To ensure that users are not surprised by new functions, we should think very carefully about what we renew and how we guarantee that existing scripts are not affected.
One idea might be not to redevelop all the functions, but to implement providers, for example, that are responsible for generating the data in the Python Faker library.
The ticket is the result of a discussion at the RBCN25 Community Day.
We must not forget that the FakerLibrary is used by a group of users in productive test cases or tasks.
To ensure that users are not surprised by new functions, we should think very carefully about what we renew and how we guarantee that existing scripts are not affected.
One idea might be not to redevelop all the functions, but to implement providers, for example, that are responsible for generating the data in the Python Faker library.