loading translations in two formats: the .mo format used by gettext and related tools, and a simple .csv format. An application will generally call either tornado.locale. load_translations or tornado.locale the second string is chosen. Applications should call one of load_translations (which uses a simple CSV format) or load_gettext_translations (which uses the .mo format supported by gettext and related tools) locale.load_translations(directory: str, encoding: str | None = None) → None Loads translations from CSV files in a directory. Translations are strings with optional Python-style named placeholders (e.g

gettext [https://docs.python.org/3/library/gettext.html#module-gettext] and related tools, and a simple .csv format. An application will generally call either tornado.locale.load_translations or tornado.locale the second string is chosen. Applications should call one of load_translations (which uses a simple CSV format) or load_gettext_translations (which uses the .mo format supported by gettext [https://docs html#None] = None) → None [https://docs.python.org/3/library/constants.html#None] Loads translations from CSV files in a directory. Translations are strings with optional Python-style named placeholders (e.g

exports the function name read, but the CSV.jl package also provides CSV.read. If we are going to invoke CSV reading many times, it would be convenient to drop the CSV. qualifier. But then it is ambiguous referring to Base.read or CSV.read: julia> read; julia> import CSV: read WARNING: ignoring conflicting import of CSV.read into Main Renaming provides a solution: julia> import CSV: read as rd Imported identifier is brought into scope. For example using CSV: read as rd works, but using CSV as C does not, since it operates on all of the exported names in CSV. Mixing multiple using and import statements

exports the function name read, but the CSV.jl package also provides CSV.read. If we are going to invoke CSV reading many times, it would be convenient to drop the CSV. qualifier. But then it is ambiguous referring to Base.read or CSV.read: julia> read; julia> import CSV: read WARNING: ignoring conflicting import of CSV.read into Main Renaming provides a solution: julia> import CSV: read as rd Imported identifier is brought into scope. For example using CSV: read as rd works, but using CSV as C does not, since it operates on all of the exported names in CSV. Mixing multiple using and import statements

exports the function name read, but the CSV.jl package also provides CSV.read. If we are going to invoke CSV reading many times, it would be convenient to drop the CSV. qualifier. But then it is ambiguous referring to Base.read or CSV.read: julia> read; julia> import CSV: read WARNING: ignoring conflicting import of CSV.read into Main Renaming provides a solution: julia> import CSV: read as rd Imported identifier is brought into scope. For example using CSV: read as rd works, but using CSV as C does not, since it operates on all of the exported names in CSV.CHAPTER 17. MODULES 223 Mixing multiple using

exports the function name read, but the CSV.jl package also provides CSV.read. If we are going to invoke CSV reading many times, it would be convenient to drop the CSV. qualifier. But then it is ambiguous referring to Base.read or CSV.read: julia> read; julia> import CSV: read WARNING: ignoring conflicting import of CSV.read into Main Renaming provides a solution: julia> import CSV: read as rd Imported identifier is brought into scope. For example using CSV: read as rd works, but using CSV as C does not, since it operates on all of the exported names in CSV.CHAPTER 17. MODULES 223 Mixing multiple using

exports the function name read, but the CSV.jl package also provides CSV.read. If we are going to invoke CSV reading many times, it would be convenient to drop the CSV. qualifier. But then it is ambiguous referring to Base.read or CSV.read: julia> read; julia> import CSV: read WARNING: ignoring conflicting import of CSV.read into Main Renaming provides a solution: julia> import CSV: read as rd Imported identifier is brought into scope. For example using CSV: read as rd works, but using CSV as C does not, since it operates on all of the exported names in CSV.CHAPTER 17. MODULES 223 Mixing multiple using

exports the function name read, but the CSV.jl package also provides CSV.read. If we are going to invoke CSV reading many times, it would be convenient to drop the CSV. qualifier. But then it is ambiguous referring to Base.read or CSV.read: julia> read; julia> import CSV: read WARNING: ignoring conflicting import of CSV.read into Main Renaming provides a solution: julia> import CSV: read as rd Imported identifier is brought into scope. For example using CSV: read as rd works, but using CSV as C does not, since it operates on all of the exported names in CSV. Mixing multiple using and import statements

exports the function name read, but the CSV.jl package also provides CSV.read. If we are going to invoke CSV reading many times, it would be convenient to drop the CSV. qualifier. But then it is ambiguous referring to Base.read or CSV.read: julia> read; julia> import CSV: read WARNING: ignoring conflicting import of CSV.read into Main Renaming provides a solution: julia> import CSV: read as rd Imported identifier is brought into scope. For example using CSV: read as rd works, but using CSV as C does not, since it operates on all of the exported names in CSV.CHAPTER 17. MODULES 223 Mixing multiple using

exports the function name read, but the CSV.jl package also provides CSV.read. If we are going to invoke CSV reading many times, it would be convenient to drop the CSV. qualifier. But then it is ambiguous referring to Base.read or CSV.read: julia> read; julia> import CSV: read WARNING: ignoring conflicting import of CSV.read into Main Renaming provides a solution: julia> import CSV: read as rd Imported identifier is brought into scope. For example using CSV: read as rd works, but using CSV as C does not, since it operates on all of the exported names in CSV.CHAPTER 17. MODULES 223 Mixing multiple using